|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
This should be fairly trivial to add. Unfortunately arbitrary tools may use that exit code to indicate failure, just like exist code 1, or 5, or anything non-zero, and starting to mark builds as unstable (and continue execution!) is a very backwards incompatible change, so won't be added.
The only compatible solution I could think of would be an 'Advanced' option to designate specific exit codes for a shell script/batch file builder to indicate 'Unstable'.