We Halved Go Monorepo CI Build Time

Re:We Halved Go Monorepo CI Build Time by prestoooooo on Sunday June 26, 2022 @09:06AM (#31883542)

Pros

* Breaking changes can be done at once. Very helpful for runtime deps.

* No chance that a repo is out of date.

* Upgrades are atomic (may be hard to test a system in a half state).

[ Parent | on HN ]

Re:We Halved Go Monorepo CI Build Time by erik_seaberg on Monday June 27, 2022 @02:19AM (#31891185)

While you’re deploying, production is going to be in a half-upgraded state (or maybe half rolled-back!), so it’s pretty important to be able to test that.

[ Parent | on HN ]

Re:We Halved Go Monorepo CI Build Time by iambvk on Monday June 27, 2022 @10:39PM (#31903497)

This depends on the deployment model. I am curious, how does your release and deployment looks like?

[ Parent | on HN ]

Re:We Halved Go Monorepo CI Build Time by erik_seaberg on Tuesday June 28, 2022 @02:54AM (#31904915)

Release is a privileged tool pushing to Git. Deployment is incremental across a small but growing number of containers running a microservice, so both old and new code might be running concurrently for up to a couple of hours. Percentage experiments are pretty common, which means both old and new paths actually have to work in the same commit.

[ Parent | on HN ]