Practice essential collocations for build pipelines in IT and software development.
0 / 5 completed
1 / 5
The team configured a GitHub Actions workflow to ___ pipeline automatically on every pull request.
Trigger the pipeline is the standard CI/CD collocation for initiating an automated build process in response to a code event. 'Start along' and 'kick off around' are informal. 'Run out' does not convey the event-driven nature of pipeline triggering.
2 / 5
The pipeline was configured to ___ stages sequentially: lint, test, build, and then package.
Run stages is the standard CI/CD collocation for executing the ordered steps in a pipeline. 'Execute along' and 'process around' are informal. 'Complete out' implies finishing rather than actively executing the pipeline steps.
3 / 5
The build job was configured to ___ artefacts to the company's Artifactory instance after a successful build.
Publish artefacts is the standard DevOps and CI/CD collocation for making build outputs available in a package or artefact repository. 'Upload along' and 'push around' are informal. 'Release out' is too generic and does not specify the artefact publishing process.
4 / 5
The team adopted a ___ fast strategy by stopping the pipeline immediately when any test failed.
Fail fast is the standard CI/CD engineering collocation for immediately halting a pipeline upon the first failure to provide rapid feedback. 'Stop along' and 'exit around' are informal. 'Break out' implies exiting a loop rather than a deliberate fail-fast strategy.
5 / 5
The final pipeline stage was configured to ___ to the staging environment automatically after all tests passed.
Deploy to an environment is the standard DevOps collocation for delivering a built artefact to a target execution environment. 'Push along' and 'ship around' are informal. 'Release out' is not a standard phrase for environment-specific deployment.