Hi Andrew,

Could you confirm it happens when you are using a Scriptler script? And not with a Groovy script? If so, it is duplicated of JENKINS-39620. The issue is fixed in master branch, waiting for a user to test in his test server, and then we are ready to release a 1.5.2 version that fixes this issue.

And if you confirm it's scriptler, and this issue is duplicate of JENKINS-39620; if you could confirm that the hpi binary attached to that issue works for you, we can release a new version in a couple of hours (need my keys, in my home computer).

Otherwise after the other user can test the change and - hopefully - confirm it works for him, we'll have a release tomorrow evening.

Thanks Bruno. Great to hear. And thank you for replying so quickly. Talk about service!!!

I have downgraded to Jenkins 2.25. Issue still persists.

Yes, I am using a Scripter script (for all our ActiveChoice Parameter needs).

Apologies for raising a duplicate issue (was on the critical path and wanted to get it recorded just in case it wasn't as this is such critical functionality)

Reason we did not see the issue before now (we have been on Jenkins 2.25 for a few weeks waiting for recent issues with core to stablise - I upgraded from 2.25 to 2.30, whereas normally I upgrade every week) is because our jobs have been so stable that I have not had to make any changes.

Until this morning that is when I needed to make some small unrelated changes to support a new DEMO environment.

My current work around is to edit the job config xml directly and restart the Jenkins service (If I don't restart Jenkins doesn't reload the updated config.xml)

>Thanks Bruno. Great to hear. And thank you for replying so quickly. Talk about service!!!

Don't mention it. It's the least I can do after introducing this issue

>Yes, I am using a Scripter script (for all our ActiveChoice Parameter needs).

Excellent. Marking the issue as duplicate.

>Apologies for raising a duplicate issue (was on the critical path and wanted to get it recorded just in case it wasn't as this is such critical functionality)

No apologies needed, on the contrary, you did indeed the right and doing that definitely makes it easier to maintain the plug-in, and helps other users too. Thanks for reporting it.

>My current work around is to edit the job config xml directly and restart the Jenkins service (If I don't restart Jenkins doesn't reload the updated config.xml)

Glad you found a work around. If you are OK with waiting till tomorrow evening NZ time for 1.5.2, then we just have to wait till JENKINS-39620's fix is confirmed to be good. Otherwise, if you'd like to have the new version available in the update center tomorrow morning, give it a try in a test environment to the latest hpi attached to the JENKINS-39620 issue.

Once anybody else confirms it works, I'll cut a release.

Cheers
Bruno

Thanks Bruno,

As the issue is occurring with Jenkins 2.25 my plan is to:

1. Upgrade to the new new release of the plugin when it is available
2. Confirm the issue is resolved by updating config, saving and confirming changes stick
3. Re-Upgrade to Jenkins 2.31 and repeat step 2 to ensure it is not related to recent Core issues.

Cheers,
Andrew

1.5.2 released about one hour ago with the fix for this issue

1. Done
2. Tested Successfully
3. Done and Tested Successfully

Thank you