Allow Skip CI for Release API
Problem to solve
In the current state, a pipeline is triggered with the creation of each release. We need to ensure it doesn’t in turn trigger further pipelines.
Intended users
Proposal
After multiple discussions (check threads below) on the best way to handle this feature request, we agreed to provide documentation and examples on how users could accomplish this instead of building this as a new feature:
-
Document the configuration needed to skip tag pipelines on release creation in releases documentation. (Merge request: !89487 (merged))
Below is an example for how this could be done in .gitlab-ci.yml
:
workflow:
rules:
- if: $CI_COMMIT_TAG
when: never
-
Create an includable extension under "GitLab CI CD Extensions" to refer to in documentation.
Further details
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.