Bug 467534 - Parameters passed by upstream job not resolved in downstream job parameter
Summary: Parameters passed by upstream job not resolved in downstream job parameter
Status: NEW
Alias: None
Product: Hudson
Classification: Technology
Component: Core (show other bugs)
Version: 3.2.2   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Winston Prakash CLA
QA Contact: Geoff Waymark CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-18 18:27 EDT by Lidia Marchioni CLA
Modified: 2015-05-18 18:27 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lidia Marchioni CLA 2015-05-18 18:27:17 EDT
I have two jobs: job1 and job2, where job2 is triggered by job1 passing current job parameters.  

Job1 has the following parameters defined:

job1 param A: a
job1 param L: l
job1 param Z: z


Job2 has the following parameters defined:

job2 param G: ${A}_${L}_${Z}
job2 param M: ${A}_${L}_${Z}
job2 param ZZ: ${A}_${L}_${Z}


When I print all the parameters in job2 this is what I get:


+ echo 'job1 param A: a'
job1 param A: a
+ echo 'job1 param L: l'
job1 param L: l
+ echo 'job1 param Z: z'
job1 param Z: z
+ echo 'job2 param G: a_${L}_${Z}'
job2 param G: a_${L}_${Z}
+ echo 'job2 param M: a_l_${Z}'
job2 param M: a_l_${Z}
+ echo 'job2 param ZZ: a_l_z'
job2 param ZZ: a_l_z


It looks like parameters passed by job1 are being resolved again in job two based on alphabetical order and hence the references do not work as expected.  The expectation is that all parameters defined in job2 would have a value of a_l_z.