[
https://issues.jenkins-ci.org/browse/JENKINS-13755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory Boissinot closed JENKINS-13755.
---------------------------------------
Resolution: Fixed
In my option, Jenkins doesn't have to be in charge of the exit code.
To ignore test in failure with Ant, just check the haltonfailure of the Junit
task is set to false (http://ant.apache.org/manual/Tasks/junit.html).
You are able to use the xUnit Jenkins plugin to set the build status to fail or
unstable if the number of failed tests exceed a specified value (threshold
feature).
https://wiki.jenkins-ci.org/display/JENKINS/xUnit+Plugin
> Add option to continue, even if the java exit code is not 0
> -----------------------------------------------------------
>
> Key: JENKINS-13755
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13755
> Project: Jenkins
> Issue Type: Improvement
> Components: ant
> Affects Versions: current
> Reporter: alex o
> Assignee: Gregory Boissinot
> Labels: ant, exit_code
>
> if you run a netbeans created ant script and a unit test fails, the java exit
> code is 1 which will completely halt the jenkins build process. A unit test
> failure may or not be critical issue and it should at least be an option to
> ignore the process's exit code
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
