Inconsistent and incorrect use of env. prefix before Gitlab predefined variables in Maven repository page
Problem to solve
The use of "env." prefix within the Maven repository documentation is consistent and results in pipeline failures as "${env.predefined_variable_name}" evaluates to an empty value.
Further details
In the Maven repository documentation we can see that Gitlab predefined variables have an "env." prefix. If we see the section on using maven from CI/CD you can see that the use of "env." prefix is inconsistent. The pipeline actually works only when this prefix is removed.
Proposal
Remove the prefix "env." from all the code snippets within the Maven repository documentation
Who can address the issue
No expertise required
Other links/references
Edited by Shaiju Janardhanan