Stub CI_COMMIT_BRANCH in specs covering latest tag
What does this MR do?
Stub CI_COMMIT_BRANCH
in specs that differentiate between stable branches and regular feature branches so that they don't fail in stable branches.
Fixes errors like: https://gitlab.com/gitlab-org/omnibus-gitlab/-/jobs/2612263935
Introduced by: !6118 (merged)
Related issues
Checklist
See Definition of done.
For anything in this list which will not be completed, please provide a reason in the MR discussion
Required
-
Merge Request Title, and Description are up to date, accurate, and descriptive -
MR targeting the appropriate branch -
MR has a green pipeline on GitLab.com -
Pipeline is green on dev.gitlab.org if the change is touching anything besides documentation or internal cookbooks -
trigger-package
has a green pipeline running against latest commit
Expected (please provide an explanation if not completing)
-
Test plan indicating conditions for success has been posted and passes -
Documentation created/updated -
Tests added -
Integration tests added to GitLab QA -
Equivalent MR/issue for the GitLab Chart opened
Edited by DJ Mountney