When you have a parametrised build trigger using a build parameter to select a list of builds to trigger the following happens: 1st build after a jenkins restart works fine, while the 2nd keeps the parameter values from the 1st. (Or at least it seems so: please find details/proofs in the attachments).

Still no clue if this comes directly from this plug-in or from some other related to it or (maybe) it's a core jenkins issue (the jenkins was update really often lately plus I had new plug-ins installed/updated so it's hard identify a reason).

The "test" build I used is following:

• trigger builds from the CCC variable (non-conditional build step)
• trigger another build only if BBB is true (conditional build step)

In the 1st run I select BBB=true, CCC="TEST 2, TEST3"; and the build proceeds as expected triggers builds TEST 2 & TEST 3, and then a conditional build step.

In the 2nd run I select BBB=false, CCC="TEST 1"; and proceeds in a very weird manner it still triggers builds TEST 2 & TEST 3, like before - so I assume it somehow takes the old value for the parameter CCC, but then doesn't trigger the conditional build - so I assume it now takes the current value for the parameter BBB.

I am pretty sure it was working fine before (a few weeks ago) I have no proof for it.