How to Set Up a GitLab CI/CD Job Dependent on Multiple Previous Jobs

Описание: Learn how to create a `GitLab CI/CD` job that depends on two other jobs effectively, ensuring successful integration and deployment.
---
This video is based on the question https://stackoverflow.com/q/77780264/ asked by the user 'TheBestPlayer' ( https://stackoverflow.com/u/16249829/ ) and on the answer https://stackoverflow.com/a/77780394/ provided by the user 'Ext3h' ( https://stackoverflow.com/u/2879325/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, comments, revision history etc. For example, the original title of the Question was: Gitlab CI/CD one job depending on 2 other jobs

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Set Up a GitLab CI/CD Job Dependent on Multiple Previous Jobs

When working with GitLab CI/CD, it is common to structure our jobs in such a way that some jobs depend on the successful completion of one or more previous jobs. However, it can be tricky to get it right, especially when a job needs to retrieve artifacts from multiple jobs. In this guide, we will discuss a user scenario where a release_job needs to depend on two other jobs: build and prepare_job. If you find yourself stuck in a similar situation, read on to discover how to solve this issue effectively.

The Problem

In our example, the user has a pipeline consisting of three jobs — prepare_job, build, and release_job. They encountered an error when trying to make release_job dependent on both prepare_job and build. The error message read:

[[See Video to Reveal this Text or Code Snippet]]

This indicates that the release_job is trying to access artifacts from prepare_job, but the GitLab runner does not recognize it as being in a previous stage due to job rules.

Understanding Job Dependencies in GitLab CI/CD

To solve the issue, we need to understand the dependency model in GitLab CI/CD. The keyword needs allows jobs to declare which jobs or artifacts they depend on, bypassing the default stage order. Here are some key considerations:

Stage Order: Jobs declared in stages run sequentially by default, but needs can rearrange this order.

Job Rules: Each job can have rules specifying when they should run based on certain conditions (like tags or branches).

Optional Dependencies: If a job that is not declared as optional fails, it will result in a pipeline failure.

The Solution

To ensure that our release_job takes dependencies on both build and prepare_job, we need to ensure both jobs can run under the same conditions. Here’s how we can modify the jobs accordingly:

Step 1: Align Job Rules

Make sure that the rules for prepare_job are aligned with release_job so that both jobs can run under similar conditions. Here's an example adjustment:

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Ensure Proper Usage of needs

In your release_job, you are already correctly using the needs keyword to depend on both build and prepare_job. Just ensure the rules allow for both jobs to be run based on the conditions defined.

Step 3: Test Your Pipeline

After making these changes, run your pipeline with a suitable commit tag. Make sure that both prepare_job and build jobs complete successfully so that release_job can access their artifacts.

Conclusion

By carefully aligning the job rules and properly declaring dependencies using the needs keyword, you can effectively set up a GitLab CI/CD pipeline with jobs that depend on outputs from multiple previous jobs. This approach not only organizes your job workflows but also enhances the efficiency and reliability of your CI/CD processes.

If you're facing challenges similar to this, remember that every job's rules must harmonize with its dependencies. Happy coding!