Скачать или смотреть How to Create a Nested Stage in GitLab CI/CD for Your Workflow

Learn how to effectively structure your `GitLab CI/CD` pipeline by creating a single stage that can contain multiple jobs. This guide provides a step-by-step solution and detailed explanations to help simplify your deployment process.
---
This video is based on the question https://stackoverflow.com/q/62937734/ asked by the user 'Cristian Blanco' ( https://stackoverflow.com/u/13914296/ ) and on the answer https://stackoverflow.com/a/62938946/ provided by the user 'Sergio Tanaka' ( https://stackoverflow.com/u/11127443/ ) 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, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Is there any way to make in Gitlab CI/CD a stage with two stages inside?

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 Create a Nested Stage in GitLab CI/CD for Your Workflow

In the world of Continuous Integration and Continuous Deployment (CI/CD), GitLab provides a powerful and flexible platform for managing your software builds and deployments. However, many users encounter challenges when trying to organize their pipelines in a more hierarchical structure. One such question that frequently arises is: Is there a way to create a stage in GitLab CI/CD that contains multiple jobs (or stages)?

The answer to this question is yes, and in this guide, we'll walk through how you can achieve this in your .gitlab-ci.yml file. This approach not only organizes your pipeline better but also enables you to handle multiple deployments simultaneously with ease. Let’s dive right in!

Understanding the Basics of GitLab CI/CD

Before we get into the solution, let's briefly recap the critical components of your GitLab CI/CD pipeline:

Stages: These are defined phases of your CI/CD process, such as build, test, and deploy.

Jobs: These are individual tasks that run as part of a stage. Each job can have its own script and conditions.

The Objective of Organizing Your Pipeline

In your case, you're looking to have two deployment jobs (for a website and a cloud function) under a single overarching stage called release. This not only simplifies your pipeline but also enhances readability and maintenance.

Step-by-Step Solution to Create Nested Stages

Let’s transform your existing .gitlab-ci.yml file which currently has separate stages into one cohesive stage with multiple jobs. Here's how you can do it:

1. Define Your Stage

First, define your new overarching stage, release. Open your .gitlab-ci.yml file and specify your stages as follows:

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

This step outlines that there will now be just one main stage under which all related jobs will reside.

2. Assign Jobs to the Release Stage

You will need to specify that both of your deployment jobs (deploy-website and deploy-cloud-function) belong to this newly defined stage. Here’s how:

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

3. Handling Job Execution Order

If you make this change, it's critical to note that both jobs will start executing simultaneously. If you want to avoid this, you can control when your jobs run by setting them to only start manually. You can add the following line to each job configuration:

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

This allows you to trigger the jobs manually as needed, preventing them from running simultaneously and giving you greater control over your deployment pipeline.

Updated Example Configuration

Putting everything together, your updated .gitlab-ci.yml file should look like this:

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

Conclusion

By following the structured approach outlined above, you have successfully created a unified release stage in your GitLab CI/CD pipeline, containing multiple jobs. This not only enhances the clarity of your .gitlab-ci.yml file but also allows you to manage your deployment process more effectively. Keep experimenting with the power of GitLab CI/CD to streamline and optimize your workflows!