Is it possible to supply a different value for a variable depending on whether the CI job is running on a protected branch?
A typical scenario would be to provide read-only Nexus credentials for general jobs (e.g. feature branches), but read-write credentials for the protected
master branches, which publish snapshots & releases to Nexus.
In the CI variables configuration section, I tried the following out, but met an error:
An alternative would be to use two different variable names, but this puts the burden on every CI script across projects to probe for which variable is defined (in the above case for both a username & password), which spreads complexity all over the place.
What do most people do to satisfy this use case? Any existing feature requests that are relevant?