|
|
_0.png) |
|
|
|
|
Issue Type:
|
 Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Gregory Boissinot
|
|
Components:
|
envinject, parameterized-trigger |
|
Created:
|
28/Jun/12 5:56 PM
|
|
Description:
|
A job that uses "Prepare an environment for the run" and defines some variables either in a properties file, or inline properties, does not pass these variables to child job executions.
I'm using "Trigger/call builds on other projects" and specifying a list of child jobs, and "Current build parameters" is checked.
I added an 'env' at the top of the scripts for both parent and child jobs and all of the properties defined in the parent via env injected properties are not present in the child env.
I also compared the build's "Injected environment variables" and they confirm that the parent injected properties are missing from the child env.
|
|
Environment:
|
Ubuntu 12.04.
ii jenkins 1.472 Continuous integration system written in Jav
|
|
Project:
|
Jenkins
|
|
Priority:
|
 Major
|
|
Reporter:
|
Bruce Edge
|
|
|
|
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
|
|
Locked
I have a work-around, but I don't feel it should be necessary.
If I re-specify the same properties file using the "Parameters from properties file" under the "Trigger/call builds on other projects" build action, then the properties are present in the child env.
I believe that it is still a bug however that the parent's env is not propagated to the child when "Current build parameters" is checked. It should not require that I re-specify the same properties file in two places.