Run pipelines in agreement with our release setup
Right now, we include this standard Gitlab workflow for our CI:
workflow:
rules:
- if: $CI_MERGE_REQUEST_IID
- if: $CI_COMMIT_TAG
- if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
This has some problems:
- running a pipeline for a tag is not really necessary, because the tag in our workflow is supposed to point to a commit on the main branch, which already has a pipeline according to the third rule above.
- The pipeline that runs for a tag fails, because the CI tries to use the
$CI_COMMIT_REF_NAME
as branch name, but our typical tag name0.x.y
is not the name of any branch. - There is no pipeline run for the release branch
v0.x
, because it's not attached to a merge request.
To solve this we should probably stop including the predefined Gitlab workflow
rules and write our own to match what we want.
Edited by Arie Peterson