4 ms·
hmm I dunno... If you have CD working correctly you should be shipping multiple times a day depending on the product. If there is a problem with the deploy it s
by cphoover 8y ago
hmm I dunno... If you have CD working correctly you should be shipping multiple times a day depending on the product. If there is a problem with the deploy it should be as simple as rolling back to the container image of the last version...with K8s or ECS this takes seconds.
I really hate the whole "let's plan for a midnight deploy" paradigm... and find it very unconstructive.
- sbergot 8y agoHow do you rollback a DB schema change?
- clintonb 8y agoYou deploy in phases. You only remove data in the final phase. I wrote about this at https://engineering.edx.org/django-migration-donts-f4588fd11b64 https://engineering.edx.org/django-migration-donts-f4588fd11....
- tracker1 8y agoYou can absolutely push to development, qa, uat, demo even... just don't deploy to production.
- karmakaze 8y agoThis point seems targeted more toward those who deploy infrequently, e.g. weekly deploy on Tuesdays. When working on a few microservices with several deploys per service per day per programmer-pair, not deploying on a Friday means a ~20% productivity reduction. We had one of thosr days as there was an important demo day and our work got blocked in staging. When it finally does deploy to prod, you're exposing your users to all the changes at once and if there's an issue it's much harder to isolate the cause. Our basic rule is don't deploy and leave any day of the week. If something does happen on the weekend, we're unofficially on-call via slack. I can only remember this happening maybe twice in two years.