Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
ldnandy17yEnabling deployments any day forced stable deployments... Ain't got time to be stay'n late! Test everything and deploy often!
-
devnope5697y1. Have a backup in place
2. Know restore works
3. Know what changes
4. Know what will break on the way
5. Assume what will break
6. Brace yourself for the unexpected
7. Arrange stand ins at management, dev, op, hardware people, sec
8. Arrange points of return and points of no return
9. Remove as many moving parts of these parts as possible -
devnope5697y10. Do retrospectives, post mortems if needed - strive to make the next deployment less horrible
Until you can trigger deployment on Friday 16 o'clock, write a mail to all people, who are impacted by the deployment, go take a dump, get back to your desk, check, if everything is still doing and then have a nice weekend -
mihirkh1427yI like the never deploy and get therapy instead to not feel useless approach. Has been working for me quite well.
-
coderme6557yI deployed a large update to our custom ORM at 7PM today and wasn't even worried!
...
Yeah, now that I think about it, I should probably be worried. -
If I haven't deployed by 3pm I'll deploy it in the morning. 99% of the time now deployments go fine without an issue but I'd rather not end up late picking up my kid because I broke something not paying attention.
"Avoid deploying on Fridays".
Today is Friday.
Today I had to deploy.
Today I won't go home :(
rant
deploy friday sad