Currently, users of "Execute shell" builds must fetch the jenkins-cli jar and execute it in order to mark a build as unstable. For example:
will flag as unstable and exit.
That works, but it's a right pain. The alternative is text-finder plugin string matching, which is arguably worse.
What'd be ideal is to let the return code 2 mean "unstable" to Jenkins. So one could just replace the above with:
I'll see what's involved in adding this, but wanted to put the idea out.