Deploys that don’t need a developer’s laptop
Production releases used to be built by hand on someone’s machine. Afterwards, approving a merge was the whole deploy.
- For
- Before CCC, as an employee at a national retailer and a market research firm
- When
- 2021–2025
The situation
At one company, developers built production code on their own machines, copied it over by hand, and stopped and restarted services manually. There was no standard Git workflow, so random changes could end up in production. At another, merge conflicts were a recurring tax and code checks happened late or not at all.
What I did
A Git workflow the team followed, with branch protections and written rules, then pipelines that build and test every change and deployments driven by templates. Older .NET Framework apps that couldn’t run in containers got their own build server.
What changed
Production deploys could be done from any non-developer’s PC: approve the merge and that’s it. Merge conflicts became rare, and code stopped reaching production by accident.
Built with
- Azure DevOps
- Bitbucket Pipelines
- Docker
- PowerShell
- .NET