How to use manual jobs with `needs:` relationships

In GitLab CI/CD, a bug affecting pipeline behavior was addressed in version 13.12, particularly concerning manual jobs that require user intervention before execution. Previously, if a job needed a manual job that wasn't triggered, the pipeline would get stuck, halting subsequent jobs. Manual jobs are now considered optional by default, and pipelines no longer stop if such jobs are not triggered, allowing subsequent jobs to run. If users prefer the previous behavior where a pipeline waits for manual jobs to execute, they can override the default setting by changing the allow_failure attribute to false, making these manual jobs mandatory and thus blocking the pipeline until they are run. The update introduces flexibility with the needs keyword, enabling Directed Acyclic Graphs (DAG) to optimize pipeline execution by defining dependencies beyond stage ordering.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.