Скачать или смотреть How to Replace only Syntax with rules in GitLab CI/CD

Learn how to effectively replace the `only` keyword in your GitLab CI/CD configurations with the more versatile `rules` syntax. Improve the clarity and maintainability of your CI configurations.
---
This video is based on the question https://stackoverflow.com/q/63908297/ asked by the user 'Bellini' ( https://stackoverflow.com/u/14283350/ ) and on the answer https://stackoverflow.com/a/63913192/ provided by the user 'amBear' ( https://stackoverflow.com/u/14277932/ ) 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: Gitlab CI: Replace only: *allowed_branches with rules:

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.
---
Understanding the Transition from only to rules in GitLab CI/CD

GitLab CI/CD is a powerful tool to automate your software delivery process. Within the realm of configuration, you might encounter situations where certain keywords and syntaxes evolve for better functionality and flexibility. One common request is to transition from using the only syntax to the more sophisticated rules syntax for job conditions. This guide will guide you through the process of making this transition seamlessly.

The Problem: Using only in GitLab CI/CD

In GitLab CI/CD, the only keyword is traditionally used to specify which branches or tags a particular job should run. For instance, you might have a job defined in your .gitlab-ci.yml configuration file that looks like this:

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

Here, my_branches is defined as follows:

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

While this setup works for its intended purpose, as GitLab continues to evolve, it is recommended to adopt the rules syntax as it provides greater control and flexibility over job execution conditions.

Solution: Replacing only with rules

To replace the only syntax with rules, you'll need to express the conditions under which the job should run. Here’s how you can rewrite the job definition:

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

Breaking Down the New Syntax

Using rules:

Each entry under rules sets a condition for when the job should run. If any of the conditions are true, the job will execute.

Branch Conditions:

The conditions include:

Checking if the commit branch equals "master"

Checking if the commit branch equals "release"

Using a regex to match any branches that start with "hotfix/"

Limitations:

It's important to note that unlike only, where you could reference branch definitions via anchors or aliases, rules does not support this anchoring, meaning you will need to define conditions explicitly within each job.

Conclusion

Transitioning from the only syntax to the rules syntax in GitLab CI/CD not only modernizes your configuration but also equips you with a more versatile mechanism for controlling job execution. By utilizing conditions such as branch checks through rules, you can enhance both the clarity and maintainability of your CI/CD pipelines.

This change might require some adjustments to your CI configurations, but the benefits of clearer and more flexible job control are well worth the effort. Happy coding!