“Create a CI/CD pipeline: a code commit builds an application artifact, runs automated tests and a security scan, deploys to staging, runs smoke tests, receives release approval, deploys to production, and checks production health. Route test failures to fixing code and committing again, security failures to remediation, declined approval to holding the release, and failed production health to rollback.”
Comprenez les décisions qui le sous-tendent.
Do not deploy an artifact that fails automated tests.
Remediate a failed scan before continuing the release.
Hold a release that has not been approved.
Roll back if the deployed version fails its production check.
Use this for services with build, test, staging, production, and rollback stages.
Questions fréquentes
Why include a staging environment?
Staging provides a deployed environment where the team can run checks before exposing the release to production traffic.
What is a smoke test?
A smoke test is a short check that confirms the main functions of a deployed application are available before deeper use.
Why show rollback in the same pipeline?
A rollback is part of the release process when production health checks fail, so the response should be visible with the forward path.