You are signed in. Close

You are signed out. Close

Thank you. Your subscription has started. Close

Thank you. You will get an email when a new comic comes out. Close

We could not confirm your payment. If you paid, use the link "Sign in" at the bottom of the page. Close

Something went wrong on our side. Please try again in a moment. Close

Previous episode Pull requests and branch protection: how a team keeps main green

How CI/CD works: why releasing code every day is safer than once a month

Build artifacts: why you build an app once and ship that same copy

The version of an app that was tested and the version that goes live can be two different apps, even when they come from the same code. How that happens, and why careful teams build their app only once.

  1. 1 Until now, on every release day, Rono built the app again on his own laptop, from the code in main, and copied what came out onto production.release dayRonobuildproduction

    Until now, on every release day, Rono built the app again on his own laptop, from the code in main, and copied what came out onto production.

  2. 2 The version the team had tested during the week was another build of the same code. In between, one of the app's dependencies, ready-made code it uses, got a new version, so the app that went live was one nobody had tested.Tuesday buildtesteddependencyv2.1Sunday buildshippeddependencyv2.2≠not the same app

    The version the team had tested during the week was another build of the same code. In between, one of the app's dependencies, ready-made code it uses, got a new version, so the app that went live was one nobody had tested.

The rest of this episode is for subscribers

Subscribe to read every premium episode. You can cancel when you want.

Paid yearly: $99 instead of $119.88

Next episode Staging vs production: why an app is tested on a copy first

Share this comic

More comics