[
https://issues.jenkins-ci.org/browse/JENKINS-10436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160334#comment-160334
]
Marco Vermeulen commented on JENKINS-10436:
-------------------------------------------
Has anyone taken a further look into this?
This is a major issue and has been untouched for going on a year.
> Jenkins Environment Variables are not set when using a freestyle "Invoke
> top-level Maven Targets" that is restricted to execute on a slave
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JENKINS-10436
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10436
> Project: Jenkins
> Issue Type: Bug
> Components: maven2
> Environment: jenkins 1.421
> Reporter: Scott MacDonald
>
> When creating a free style build and selecting "invoke top-level Maven
> targets", Jenkins exposes functionality to utilize jenkins environment
> varibale references.
> "The same variables can be used in command-line arguments (as if you are
> invoking this from shell). For example, you can specify
> -DresultsFile=${WORKSPACE}/${BUILD_TAG}.results.txt"
> When the job is restricted to run on a slave, the values of those environment
> variables should be based on the slaves environment variables name-value
> pairs. The salve name value pairs are not being substituted as they do in a
> regular maven based job.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
