A city release process still waits for a monthly weekend freeze, but leadership wants every commit to trigger automated build and test instead. What DevOps shift does this describe?
Select an answer to reveal the explanation.
Short Explanation
Monthly big-bang weekends are the old fire drill. CI/CD flips that: every commit gets built and tested automatically so problems show up Tuesday at 2 p.m., not during a Saturday cutover. Less heroics, more conveyor belt.
Full Explanation
Continuous integration and continuous delivery or deployment automate build and test (and often release) on frequent code changes, reducing reliance on infrequent manual release events. Municipal teams adopt CI/CD to shorten feedback loops and cut toil. Dropping automation in favor of PDFs, USB couriers, or laptop-only deploys moves away from that model.