CI/CD pipelines have their own precise language. Practise the collocations engineers use when shipping and managing releases.
0 / 5 completed
1 / 5
Fill in: 'Merging to main will automatically ___ the CI/CD pipeline.'
We 'trigger a pipeline' — 'trigger' is the technical collocation for causing an automated process to begin. 'Start a pipeline' is acceptable but less precise; 'run' is used as an intransitive verb (the pipeline runs); 'kick' requires 'kick off' to be idiomatic.
2 / 5
Fill in: 'We chose to ___ the new API version ___ to 5% of users before a full release.'
We 'roll out gradually' — 'roll out' is the standard deployment collocation meaning a staged release; 'gradually' is its natural adverbial partner. 'Push out slowly' is informal; 'send carefully' and 'give step by step' are not idiomatic in deployment contexts.
3 / 5
Fill in: 'The release manager will ___ a release at 4 PM once all regression tests pass.'
We 'cut a release' — a software industry collocation meaning to create and tag a formal release build. 'Make a release' is informal; 'do a release' is conversational; 'produce a release' is technically correct but not standard industry idiom.
4 / 5
Fill in: 'After staging tests pass, the build will be ___ to production automatically.'
We 'promote to production' — 'promote' is the CI/CD-specific term for advancing a build through pipeline stages. 'Moved to production' lacks the stage-gate connotation; 'sent' is too informal; 'pushed' refers to source-control operations, not pipeline promotion.
5 / 5
Fill in: 'The incident was severe enough that we had to ___ the deploy within minutes.'
We 'roll back a deploy' — 'roll back' is the established DevOps collocation for reverting a deployment to a previous stable state. 'Undo' and 'revert' are used for code changes in version control; 'cancel' applies to pending actions, not completed deployments.