I am trying to use the new feature from https://issues.jenkins-ci.org/browse/JENKINS-23786 together with the "Execute Windows batch command" build step type to have a certain error level/return code of the batch command lead to result "Unstable" instead of "Failed".

This works flawlessly when it is configured initially (steps below), but if the Jenkins service is restarted (or if you do "Manage Jenkins" -> "Reload Configuration from Disk" ), the setting is lost.

To reproduce:

• create a new "Freestyle project item" (e.g. "myUnstableTest")
• "Add build step" -> "Execute Windows batch command"
  • "Command": exit 1
  • "Advanced" -> "ERRORLEVEL to set build unstable": 1
• "Save"

• "Build Now"
  -> the test result is "Unstable" (as expected)

• "Jenkins" -> "Manage Jenkins" -> "Reload Configuration from Disk"
• "Build" item "myUnstableTest" again
  -> the test result is now "Failed"

If you check the configuration of "myUnstableTest", you will see that the setting for "ERRORLEVEL to set build unstable" is now empty.

Interestingly, file jobs\myUnstableTest\config.xml still contains the correct setting

<builders>
<hudson.tasks.BatchFile>
<command>exit 1</command>
<unstableReturn>1</unstableReturn>
</hudson.tasks.BatchFile>
</builders>

It appears as if the "<unstableReturn>" value is not read from the config file correctly.