-
Improvement
-
Resolution: Unresolved
-
Trivial
-
None
When utilizing slave specific environment variables, it would be nice if the "value" was included in the console output for the build instead of the variable name For example, suppose I define a slave specific environment variable, call foo, whose value is bar, and then invoke a maven job on that slave similiar to "clean install -DmyBuildSetting=${foo}"
When I look at the maven build output, I see
��Executing Maven: -B -f /log/jenkins/.jenkins_slaves/dbVerify1/workspace/trunk_core-apps-db/pom.xml clean install -DmyBuildSetting=${foo}
It would much better if in additional to knowing that a jenkins variabel was used in invocation the build, but also tracing the he actual value that was used.
�Executing Maven: -B -f /log/jenkins/.jenkins_slaves/dbVerify1/workspace/trunk_core-apps-db/pom.xml clean install -DmyBuildSetting=${foo}
�Executing Maven: -B -f /log/jenkins/.jenkins_slaves/dbVerify1/workspace/trunk_core-apps-db/pom.xml clean install -DmyBuildSetting=bar
Having both the value in the trace output, along with knowledge that a Jenkins variable substitution occurred, is much more useful when investigating build failures (especially failures that you suspect are because Jenkins is not properly substituting your variable)