Skip to content

Harmonize how (predefined) variables can be used in CI/CD

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

After years with GitLab CI/CD DevOps development one can only conclude that it quite often feel like functionality is not fully implemented.

One obvious such thing is the use of variables. Things that would seem obvious, e.g. using CI_COMMIT_TAG in include:rules:if, is not supported.

Some of these things are not able to workaround or extremely poor workarounds.

I would like:

  1. to see a matrix with all predefined variables where they can be used and where they can't be used (this will of course act as an incentive to make sure that all variables work the same and hence then there is no need for this matrix)
  2. for all variables to be available everywhere
Edited by 🤖 GitLab Bot 🤖