Once the city’s pipeline verifies a build, the same automation releases the artifact to staging without waiting for a separate weekly install crew. Which concept does this highlight?
Select an answer to reveal the explanation.
Short Explanation
When green builds roll into staging by themselves, you’re looking at continuous delivery/deployment—the ‘ship it’ half of CI/CD. The install crew’s weekly queue becomes the exception, not the rule. Automation carries the artifact the last mile.
Full Explanation
Continuous delivery and continuous deployment extend automation beyond build and test so validated artifacts are released to environments with minimal manual packaging. Municipal pipelines use this to promote consistently built packages into staging or production under policy. Air-gapping runners by default, USB-only installs, or unmanaged desktop ‘staging’ undermine that automated promotion path.