Azure Variable Defines in the GitLab CI
In the main .gitlab-ci.yml file, there are several AZURE variable declarations that seem odd to me.
One case, AZURE_TENANT_ID
is defined to itself (${AZURE_TENANT_ID}
). In a protected pipeline execution, this causes a variable override, but to the same exact value -- no effect at all. In a non-protected pipeline, where AZURE_TENANT_ID
is not defined, GitLab leaves this unmodified as ${AZURE_TENANT_ID}
. Later, when maven runs, it attempts to resolve this, leading to an infinite loop. Example output. I think this line should be removed entirely -- I don't think it adds value.
Secondly, the AZURE
, AZURE_SKIP_DEPLOY
, and AZURE_SKIP_TEST
variables seem out of place here. The presence of the AZURE
variable as true causes pipeline stages to be created for deployment and integration tests, which on a non-protected pipeline will fail anyway for lack of secrets. Better to leave this one unspecified in the CI file, so that it can be defined by GitLab based on the protection status of the pipeline.