I assume you are using the 'Trigger parameterized build on other projects'
option under Post-build Actions to trigger your Job B (if that's not the
case, how are you triggering Job B?)
To pass variable values from Job A to Job B,
After you check the box (of Trigger parameterized build on...),
Under 'Add Parameters' dropdown, select 'Predefined parameters' option.
In the box that comes up against Predefined prameters -> Parameters, add
your env variables like below:
JobBParameter=$variableA
You can add more variables as you need.
On Wednesday, May 15, 2013 12:25:13 PM UTC+5:30, zw wrote:
>
> Hi All
>
> In the build section, we selected Use Shell to include our shell scripting
> to run on a slave for job A.
> This job A triggers Job B after completion.
> Job B needs job A's paramterized parameters to run Job B task.
> We have been unable to pass the our custom environment variable value to
> Job B from A.
> We tried using
> export variableA
> in the shell script box of the build section
> and then tried setting
> JobBParameter=${variableA}
> in the post-action of parameterized parameter
> Still it doesnt work.
>
> Is there any other way to do it, to pass custom environment variable value
> to Job B ?
> We do not have the option of EnvInj plugin.
>
> Thanks
> Sincerely
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
