[JIRA] [ant] (JENKINS-1640) Environment variables not passed through to Ant tasks
Stefan Thurnherr
commented on JENKINS-1640
Environment variables not passed through to Ant tasks
Ok I tried both ${env.PATH} and ${env.USER}, where both PATH and USER are listed under "Environment variables" at jenkins-instance/systemInfo. Used in an echo task they resolve correctly and print out the same (for USER) or similar value (for PATH: jdk location gets prefixed) as shown under jenkins-instance/systemInfo.
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant] (JENKINS-1640) Environment variables not passed through to Ant tasks
Stefan Thurnherr
commented on JENKINS-1640
Environment variables not passed through to Ant tasks
FYI: Just tested using Jenkins v1.574 and ant plugin v1.2, and ${env.WORKSPACE} worked perfectly when used together with
property environment="env" /
in my build.xml.
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant] (JENKINS-1640) Environment variables not passed through to Ant tasks
evernat updated JENKINS-1640 Environment variables not passed through to Ant tasks Stefan Thurnherr Wow! It has been years since I have not heard news about an issue with a number such as JENKINS-1640. So we may be able to close an issue opened for more than 6 years. That's good news. Jesse Glick I have assigned to you, because you are a good source of confirmation for closing. Feel free to reassign to D. or whatever. Change By: evernat (08/Aug/14 8:17 PM) Assignee: JesseGlick 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant] (JENKINS-1640) Environment variables not passed through to Ant tasks
Jesse Glick commented on JENKINS-1640 Environment variables not passed through to Ant tasks @stefanthurnherr I think this issue was about something unrelated: whether environment variables defined on the Jenkins process (i.e., not something like $WORKSPACE) are picked up by forked build steps it runs. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant] (JENKINS-1640) Environment variables not passed through to Ant tasks
Jesse Glick assigned JENKINS-1640 to Unassigned Environment variables not passed through to Ant tasks I have no particular information about this. If it remains reproducible in current versions of Jenkins, someone interested should track down why and offer a fix. Change By: Jesse Glick (08/Aug/14 8:34 PM) Assignee: JesseGlick 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant] (JENKINS-1640) Environment variables not passed through to Ant tasks
evernat commented on JENKINS-1640 Environment variables not passed through to Ant tasks ok, thanks Jesse 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant] (JENKINS-1640) Environment variables not passed through to Ant tasks
evernat updated JENKINS-1640 Environment variables not passed through to Ant tasks Is it reproduced with a recent version? Change By: evernat (12/Nov/13 11:27 PM) Component/s: ant Component/s: core 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
