Re:Don't deploy on Friday and 3 other unwritten rules of sof...
by karmakaze on Thursday March 21, 2019 @03:55AM
(#19449955)
This 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.
Re:Don't deploy on Friday and 3 other unwritten rules of sof...
by tracker1 on Wednesday March 20, 2019 @05:28PM
(#19447134)
You can absolutely push to development, qa, uat, demo even... just don't deploy to production.
Re:Don't deploy on Friday and 3 other unwritten rules of sof...
by sbergot on Wednesday March 20, 2019 @03:13PM
(#19445742)
How do you rollback a DB schema change?
Re:Don't deploy on Friday and 3 other unwritten rules of sof...
by clintonb on Wednesday March 20, 2019 @03:39PM
(#19446012)
You deploy in phases. You only remove data in the final phase. I wrote about this at https://engineering.edx.org/django-migration-donts-f4588fd11....
I really hate the whole "let's plan for a midnight deploy" paradigm... and find it very unconstructive.