Bug 431487 - Parameterized Trigger plugin does not resolve variables
Summary: Parameterized Trigger plugin does not resolve variables
Status: NEW
Alias: None
Product: Hudson
Classification: Technology
Component: Plugins (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Winston Prakash CLA
QA Contact: Geoff Waymark CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-28 09:36 EDT by SK CLA
Modified: 2014-03-28 09:36 EDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description SK CLA 2014-03-28 09:36:40 EDT 
Job A has a few parameters:

Version_Minor := x
Version_Major := y
Baseline      := My_Kind_of_Baseline_${x}_${y}

as a post-build step, A triggers Job B that is using 'current build parameters'.

Within Job A, the parameter 'Baseline' get's expanded as My_Kind_of_Baseline_x_y but when Job B starts, 'Baseline' is given and used as 'My_Kind_of_Baseline_${x}_${y}'.

My workaround: I'm currently using predefined parameters, redefining my current build parameters. This way, they're getting expanded before Job B starts.