News for hackers. Stuff that matters.
Re:Improving how we deploy GitHub by paxys on Monday January 25, 2021 @02:34PM (#25907643)
If the "other stack" isn't regularly used then you can assume it will be broken when needed
Re:Improving how we deploy GitHub by cpascal on Monday January 25, 2021 @03:58PM (#25908777)
You just run the previous version of the production stack in your "dogfood/operations" stack. Once you've fully rolled out production and have vetted it, you can upgrade the other one to match production.
Re:Improving how we deploy GitHub by epidemian on Monday January 25, 2021 @08:44PM (#25911416)
With large codebases maintained by many people, sometimes it's difficult to "just" do things like that. It's a bit weird to think that no one within that large group of professional developers hasn't thought of doing a simple obvious solution. It's probably not that simple.
Re:Improving how we deploy GitHub by cutemonster on Tuesday January 26, 2021 @08:35PM (#25923214)
Lots of comments here around that say "just do it like this: ...", or "why don't you: ... it'd be good because ..."
Re:Improving how we deploy GitHub by marcinzm on Monday January 25, 2021 @10:00PM (#25911911)
And then you get hit with a subtle bug that utterly nukes your system when the year changes from 2020 to 2021. Now you can't deploy anything because both systems are down. Given Github's scale and number of engineers it's basically guaranteed that they'll hit some sort of bug like that eventually. Not all bugs act immediately.