[JIRA] (JENKINS-1640) Environment variables not passed through to Ant tasks
karlie verkest
edited a comment on JENKINS-1640
Environment variables not passed through to Ant tasks
This is happening to me too. I have some projects where the environment variables pass through just fine and others in which the same variables do not. Here's the output of one that's not working:
[echo] Workspace Directory: ${env.WORKSPACE}
[echo] Build Number: ${env.BUILD_NUMBER}
Differences between the 2 projects?
Broken project builds periodically
Broken project discards old builds
Working project is parameterized
Quite perplexed =)
UPDATE
I feel stupid. That's what happens when you forget
"env" />
My bad! Sorry I cluttered up the comment feed.
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
[JIRA] (JENKINS-1640) Environment variables not passed through to Ant tasks
karlie verkest
edited a comment on JENKINS-1640
Environment variables not passed through to Ant tasks
This is happening to me too. I have some projects where the environment variables pass through just fine and others in which the same variables do not. Here's the output of one that's not working:
[echo] Workspace Directory: ${env.WORKSPACE}
[echo] Build Number: ${env.BUILD_NUMBER}
Differences between the 2 projects?
Broken project builds periodically
Broken project discards old builds
Working project is parameterized
Quite perplexed =)
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
[JIRA] (JENKINS-1640) Environment variables not passed through to Ant tasks
karlie verkest
commented on JENKINS-1640
Environment variables not passed through to Ant tasks
This is happening to me too. I have some projects where the environment variables pass through just fine and others in which the same variables do not. Here's the output of one that's not working:
[echo] Workspace Directory: ${env.WORKSPACE}
[echo] Build Number: ${env.BUILD_NUMBER}
Quite perplexed =)
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
[JIRA] (JENKINS-1640) Environment variables not passed through to Ant tasks
Cassiano Leal
commented on JENKINS-1640
Environment variables not passed through to Ant tasks
Same problem here. I have an ant task that uses ${env.HOSTNAME} to pick up a .properties file depending on the hostname of the machine.
It turns out that that specific variable doesn't expand, although many others do just fine.
I checked System Information, and HOSTNAME is correctly set under Environment Variables. Echoing the properties filename I get this, though:
[echo] /mnt/slave/workspace/Platform_develop_Build-Common/git/Common/${env.HOSTNAME}.build.properties
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
[JIRA] (JENKINS-1640) Environment variables not passed through to Ant tasks
Vitor Pelizza
commented on JENKINS-1640
Environment variables not passed through to Ant tasks
Hi,
Talking about a little bit different problem I'm experiencing, but still related to this thread (and the one marked as duplicated):
It's not being possible to use varibles defined by Jenkins inside ant scripts.
This used to work before updating Jenkins' version. I'm just calling an ant script on post build and using ${BUILD_VERSION} inside of it, what is not working.
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
[JIRA] (JENKINS-1640) Environment variables not passed through to Ant tasks
cowwoc commented on JENKINS-1640 Environment variables not passed through to Ant tasks Diego, It makes sense that "ant" and "DISPLAY" must be executed on the same "execute shell" line. Each shell line gets executed inside a separate shell. Placing the call on a single line causes it to execute inside the same shell. 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
[JIRA] (JENKINS-1640) Environment variables not passed through to Ant tasks
Dave Kelsey commented on JENKINS-1640 Environment variables not passed through to Ant tasks I had the same problem: running Jenkins on windows ver 1.474 on windows. FLEX_HOME is set in the environment but is not found in when ant is called. I saw failures such as "cmd.exe /c "ant.bat blah blah blah" I added "set FLEX_HOME=C:\flex_sdk_4.0.0.14159A" This didn't work. then...I looked at the configuration for the Project/build. and there it was: I checked [x] "this build is parameterize" I added "String Parameter" which let me set the name/value I wanted. The build worked after that. It's tedious but it works. 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
[JIRA] (JENKINS-1640) Environment variables not passed through to Ant tasks
Dave Kelsey edited a comment on JENKINS-1640 Environment variables not passed through to Ant tasks I had the same problem: running Jenkins (ver 1.474) on windows. FLEX_HOME is set in the environment but is not found when ant is called. I saw failures such as "cmd.exe /c "ant.bat blah blah blah" in my failed build log. I added "set FLEX_HOME=C:\flex_sdk_4.0.0.14159A" to my ant.bat. This didn't work. Then...I looked at the configuration for the Project/build. and there it was: I checked [x] "this build is parameterize" I added "String Parameter" which let me set the name/value I wanted. The build worked after that. No value pulled from the environment but I can set any String Parameter I want now. It's tedious but it works. 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
