-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
Ubuntu 12.04.
ii jenkins 1.472 Continuous integration system written in Jav
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.
[JENKINS-14251] Parent injected env properties not propagated to child build jobs
Bruce Edge
created issue -
Gregory Boissinot
made changes -
| Component/s | Original: envinject [ 15893 ] | |
| Issue Type | Original: Bug [ 1 ] | New: Improvement [ 4 ] |
cjo9900
made changes -
| Assignee | Original: Gregory Boissinot [ gbois ] | New: cjo9900 [ cjo9900 ] |
Aaron Stone
made changes -
| Link |
New:
This issue duplicates |
cjo9900
made changes -
| Component/s | New: envinject [ 15893 ] | |
| Component/s | Original: parameterized-trigger [ 15592 ] | |
| Assignee | Original: cjo9900 [ cjo9900 ] | New: Gregory Boissinot [ gbois ] |
cjo9900
made changes -
| Link |
Original:
This issue duplicates |
| Workflow | Original: JNJira [ 144883 ] | New: JNJira + In-Review [ 176214 ] |
