What steps will reproduce the problem? 1. Setup a pipeline with two steps. The first step is parameterized and only echoes the parameter value back to console. The second step does not have a parameter but still echoes the value of the parameter that is propagated down from the first step. 2. Run the pipeline a few times with different parameter values. 3. Now run the manual (second) step of an old pipeline instance.

What is the expected output? What do you see instead? - The parameter value echoed by the manual (second) step of the pipeline is the value used in the latest pipeline instance, not the one that was originally used. It is expected to actually use the original parameter value instead.

What version of the product are you using? On what operating system? - Jenkins 1.446 - Build Pipeline Plugin 1.2.4-ALPHA

Please provide any additional information below. - Just to clarify, this is the sequence of events:

First run: - Param value "X" passed to first job - First job echoes "X" to console

Second run: - Param value "Y" passed to first job - First job echoes "Y" to console

Now fire the second job of the First run: - Second job echoes "Y" to console, instead of "X".

Cannot reproduce any more.