Environment, Artifact, and Release
A focused chapter on environment, artifact, and release, with practical delivery concerns, trade-offs, and the operational questions behind CI/CD work.
Where Does Your Application Actually Run?
You just finished writing an application on your laptop. Every feature works. No errors. You're satisfied. But only you can use it, right there on your
What Actually Gets Sent to Your Environments (And Why It Matters)
Picture this: your team just finished a sprint. Everyone is tired, but the release must go out tonight. A developer builds the application on their
Why Every Artifact Needs a Name and a Number
Your team builds code every day. By Friday, you have seven different artifacts sitting in your repository. Nobody remembers which one was tested, which
Deployment: The Active Act of Placing an Artifact Into an Environment
You have built your application, packaged it into an artifact, and stored it in a repository. Now what? The artifact sitting in a repository is just a
Deployment vs Release: When Users Actually Get Your New Version
Your team just finished deploying version 1.2.0 to production. The artifact is on the server, the application is running, and every health check shows
How to Know If Your Environment Is Healthy After a Deployment
You just finished a deployment. The pipeline shows green. The server logs say the new version is running. No errors during the deploy. Everything looks