A DevOps lead documents that every change for the court-records API must follow lint, then build, then test, then deploy with a manual approval before production. What CI/CD idea is this?
Select an answer to reveal the explanation.
Short Explanation
A pipeline workflow is the recipe card: lint → build → test → deploy, with a human OK before production. Order matters—don’t serve dinner before you cook. Documented stages beat ‘whatever the runner felt like today.’
Full Explanation
Pipeline workflow orchestration defines the sequence of jobs, gates, and approvals that every change must pass. Explicit ordering and controlled promotions support repeatable municipal releases. Random sequencing, skipping quality stages, or testing only after user failure undermine controlled delivery.