79

"Avoid deploying on Fridays".
Today is Friday.
Today I had to deploy.
Today I won't go home :(

Comments
  • 3
    Avoid deploying in general till you're 100% sure shit isnt going to break. Lol
  • 1
    I know that feeling. Hope you can make it with time to spare!
  • 2
    @surgiie Tell that to my boss :(
  • 1
    Enabling deployments any day forced stable deployments... Ain't got time to be stay'n late! Test everything and deploy often!
  • 1
    1. 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
  • 1
    10. 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
  • 1
    I like the never deploy and get therapy instead to not feel useless approach. Has been working for me quite well.
  • 0
    I 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.
  • 0
    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.
Add Comment