CI said the deploy succeeded
There is a moment in every incident where someone asks "wait, is the fix even deployed?" and the room goes quiet. Somebody pulls up the CI dashboard. The pipeline is green. The deploy step says success. Everyone relaxes. And then, sometimes, the incident continues — because the green checkmark was never a statement about production. It was a statement about a pipeline. Zero — b0gy's platform for…
When a CI pipeline reports a successful deploy, it indicates that a series of steps ran without error. However, this does not guarantee that the commit pushed is the one serving production traffic. The green checkmark on the CI dashboard signifies success, but it only reflects the pipeline's outcome, not the production environment.
Several real-world scenarios demonstrate that the deploy status might not align with the live commit in production. These include rollouts that kept old revisions due to failed health checks, deploying to the wrong environment, or a pipeline reporting success on a service that subsequently crashed and was rolled back. A single "deployed ✓" flag on a service can obscure critical issues where the fix is not live in the intended environment.
This is where Landed comes into play, serving as the platform's spine of deploy truth. Landed works without any application code changes, utilizing three independent methods to learn what shipped: CI ingestion, GitHub webhooks, and a liveness probe. These mechanisms reconcile the deployed commit from CI, the reported deploy from GitHub, and the live commit found by probing the running service.
Any discrepancy between these sources triggers a "drift" state, which essentially answers the crucial question, "Is the fix even deployed?" This information is presented in a services × environments grid, highlighting the live state of the developer's latest commit. By giving developers a clear view of deploy truth, Landed transforms the incident-room question into a more precise inquiry: "Is the fix deployed here?"
Furthermore, this deploy truth serves as the foundation for other platform features, such as cost analysis. For instance, if a service's daily spend increases significantly, Zero identifies the deploy that preceded the cost surge, providing the root cause rather than just an anomaly. Similarly, observability tools leverage the same deploy truth data to pinpoint the exact commit associated with error-rate spikes, facilitating targeted troubleshooting and resolution.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
