In general, marking a build as unstable for test failures is the preferred practice. It assures that test failures are visible to downstream consumers (like other jobs, the REST API, etc.).
You may want to double check if there is a setting in the Subversion tagging plugin which will allow it to tag even if the build is unstable. I'm not aware of any way to force the job to be stable when it has failing tests. Mark Waite On Fri, Mar 14, 2014 at 12:23 PM, Chris Beech <[email protected]>wrote: > Hi there, > > > > I am executing JUnits as part of my build and am publishing JUnit test > result reports as a post-build action. > > > > The problem is, if any JUnit fails it seems that the JUnit test result > publisher is changing the build status to "UNSTABLE" which means the build > isn't classed as successful therefore the SVN tagging doesn't happen... > > > > Recording test results > > Build step 'Publish JUnit test result report' changed build result to > UNSTABLE > > No Subversion tagging for unsuccessful build. > > Finished: UNSTABLE > > > > How can I control the behaviour of the JUnit test result report to not be > marking builds as unstable when tests fail/error? > > > > Thanks, > > > > Chris > > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" 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. > -- Thanks! Mark Waite -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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.
