CI/CD build, test, and staging pipeline

This CI/CD pipeline diagram focuses on the decisions that make a release repeatable. A code commit produces an application artifact, which must pass automated tests and a security scan before it reaches staging. Smoke tests in staging test the release in a deployed environment. The approval gate keeps a human decision visible where a team needs one. After production deployment, a health check determines whether the release completes or rolls back. Each unsuccessful gate leads to a named next action rather than an implied failure. Teams can adapt the labels for their build system, testing tools, environment names, and release policy while keeping the same release logic.