|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
The scenario described here does not fail with maven-plugin version 2.7 on Jenkins LTS 1.565.3 anymore.
Although the plugin is able to resolve the global environment variable key while running (see log excerpt below) the output of the "resolved" maven command line still shows the placeholder ("${VAL_UE}")
Current scenario:
build log with VAL_UE=true (excerpt):
... Parsing POMs maven31-agent.jar already up to date maven31-interceptor.jar already up to date maven3-interceptor-commons.jar already up to date ... <===[JENKINS REMOTING CAPACITY]===>channel started Executing Maven: -B -f SLAVE_HOME/workspace/maventest/pom.xml clean -Dclean.skip=${VAL_UE} [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Maven Project 4.1-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ maven.project --- [INFO] Clean is skipped. [JENKINS] Archiving disabled Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds [JENKINS] Archiving disabled[INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1.000 s [INFO] Finished at: 2014-10-15T13:56:47+02:00build log with VAL_UE=false (excerpt):
... Parsing POMs maven31-agent.jar already up to date maven31-interceptor.jar already up to date maven3-interceptor-commons.jar already up to date ... <===[JENKINS REMOTING CAPACITY]===>channel started Executing Maven: -B -f /home/cc/jenkins-slave/workspace/maventest/pom.xml clean -Dclean.skip=${VAL_UE} [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Maven Project 4.1-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ maven.project --- [JENKINS] Archiving disabled Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds [JENKINS] Archiving disabled[INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 0.969 s [INFO] Finished at: 2014-10-15T14:07:34+02:00 [INFO] Final Memory: 6M/106M [INFO] ------------------------------------------------------------------------