| ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄|
| Don't Push To Production On Friday |
|_________________|
\ (•◡•) /
\ /
——
| |
|_ |_
| ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄| 45 comments
@nixCraft Or any other day before lots of coworkers will not be available. E.g. during the week of U.S. Thanksgiving, only Monday and Tuesday are valid deploy days. @nixCraft red penguin: I pushed to prod Friday 7:45PM, closed my laptop and turned off my phone. Blue penguin: I’m the only user @nixCraft Tell me you don’t have tests, and don’t use Ansible/puppet/whatever without telling me :P @anderseknert @nixCraft It just occurred to me that deploying could also mean in-house software. That’s a different story from OS updates, 3rd party software, and network config all right. It shouldn’t be, though. You either have proper QA, or you don’t. @nixCraft Yesterday I had a release ready at 5pm, Friday. Just ready. Sitting in staging. Said to user manager/tester, we’ll release on Monday. She agreed. @nixCraft how about building the package thats going to be deployed on Sunday thirty minutes before you leave on Friday? @nixCraft we started pushing early on Tuesday morning. Post weekend surge is over and dealt with. All staff is awake and ready to deal with issues that come up. @nixCraft @nixCraft Never! Unless you have brought your sleeping bag with you. Also don't forget clean 🩲 🩲 for the weekend at the office. LOL @nixCraft @janriemer A majority of companies cannot push to production on Friday as they are far away from CI/CD/DevOps for the majority of their IT and still think in Day1/Day2. |
@nixCraft it's too late, my guy