Exporting the variable in the shell buildstep will not add them Enviroment
variables list for later buildsteps/postbuild items,
If they are needed for later buildsteps write them to a properties files
and use the envinject plugin to make them available for later buildsteps.
If you just want to
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...),
U
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 f
