Situation
How to release software safely in a small team
Short answer. Deploy with one command from a pushed commit, never by hand from a laptop. Decide the way back before each deploy: the previous version, a fix forward or a database restore. Take a restore point before database changes and run a short smoke test of the main user journey right after.
Why releases break
A release by hand depends on who does it and what they remember. Missing settings, a forgotten step or a database change with no way back turn a ten-minute fix into a lost day.
One gate before production
Make one script the only way to say ready: it runs the build, the tests and the security checks and prints pass or fail per step. Deploy only a commit that passed it.
Decide the way back first
Before each deploy, say how you go back: switch to the previous version, fix forward or restore the database. Take a restore point right before database changes.
Check production after the deploy
Run a short check against the live system, not the repository: it answers, sign-in and the main user path work with a test account, protected pages refuse anonymous visitors and the deployed version is the commit you meant to ship. When it fails, roll back.
What CDO Agent says
CDO Agent says: Before each deploy decide the way back: switch to the previous version, fix forward or restore the database. Take a database restore point right before migrations. After deploy run a short smoke test of the main journey.
Questions
What is a smoke test after a deploy?
A short automated check against the live system right after the deploy: it answers, sign-in and the main path work, protected pages stay closed and the version is the one you meant to ship.
Do we need a way back for every release?
Yes. Most bad releases are fixed in minutes when the way back was decided before, and take a day when it was not.
When is a one-click rollback enough?
When the release has no database changes and your platform rolls back with one click.
How CDO Agent helps
Describe how you release today. CDO Agent recommends the gate, the way back and the check after the deploy for your team, and you or your coding agent set them up. See pricing.