Symphony Apps Development logo — teal interlocking S monogram beside the studio wordmark
All writing

Deploying on a Friday

The rule against Friday deploys is a symptom. What has to be true before the day of the week stops mattering.

Category
DevOps
Reading time
6 min
Published
11 Feb 2025
Topics
DevOps, CI/CD, Reliability

"Never deploy on a Friday" is good advice for teams whose deployments are risky. It is worth asking why they are risky, rather than treating the calendar as the fix.

What has to be true

  • The pipeline runs the tests, and the tests fail on real regressions
  • Staging matches production closely enough to be evidence
  • A rollback exists and has been performed at least once, deliberately
  • Alerting fires on symptoms a user would notice
  • One person can deploy without a checklist in a wiki

Rehearse the rollback

An untested rollback is a hypothesis. We rehearse it during the launch sprint on every project: deploy, roll back, verify, write down how long it took.

Once that number is known and small, the day of the week stops being interesting.

Tell us what you’re trying to ship

A first call is thirty minutes and costs nothing. Bring the problem, not a spec — working out what to build is the part we are good at.

Or email office@symphonyapps.ro. We reply within one business day, in English or Romanian.