News for hackers. Stuff that matters.
Re:Ship / Show / Ask: A modern branching strategy by rajamaka on Monday September 13, 2021 @08:35AM (#28510680)
You've never seen a blue/green deployment or a DNS change without downtime?
Re:Ship / Show / Ask: A modern branching strategy by rossmohax on Monday September 13, 2021 @08:39AM (#28510720)
I've never seen _workflow_, were developer single handedly can create a well tested PR performing all necessary release steps upon merge.
Re:Ship / Show / Ask: A modern branching strategy by rajamaka on Monday September 13, 2021 @09:47AM (#28511439)
At least for cloud environments, I haven't seen a company that doesn't have such a workflow in place for a long time.
Re:Ship / Show / Ask: A modern branching strategy by rossmohax on Tuesday September 14, 2021 @03:19AM (#28521400)
What exactly goes into PRs you've seen? How do they codify these steps, such that:

- Release steps can be tested while PR is being developed. That is executed somewhere, which doesn't interfere with production or ideally other developers ongoing PR should it go bad

- Upon merge production system safely transitioned from one state to another without human intervention.

Steps, for simplicity are:

- Deploy new version of the code behind new load balancer

- Make some requests through it to verify its workig

- Switch DNS to the new load balancer IP

- Wait for old load balancer new connections to die down and remove both LB and old version of the code behind it.