react on failed tests in pipeline script

[domi]

Hi,

I’m trying to find a way how I can react on test failures. e.g. I run maven with the flag to ignore test failures so the job does not stop. But in case a test failure was discovered, I would like to send a mail or chat message - how can I do that?

sh 'mvn clean install -B -Dmaven.test.failure.ignore'
step([$class: 'JUnitResultArchiver', testResults: '**/target/surefire-reports/*.xml’])

if(testFailure) {
// send notification
}

regards Domi

[Michael Neale]

I am assuming that ignoring test failures doesn't make the shell step fail? (Ie it returns a success code?)

If so, removing that and putting try/catch around it and then the archive step in the exception handler along with email could work. There may be a better way though (as that seems clumsy)

[Andrew Bayer]

I think the Junit result archiver should mark the build as unstable if there are failures...

On Mar 21, 2016 7:16 PM, "Michael Neale" <mne...@cloudbees.com> wrote:

I am assuming that ignoring test failures doesn't make the shell step fail? (Ie it returns a success code?)

If so, removing that and putting try/catch around it and then the archive step in the exception handler along with email could work. There may be a better way though (as that seems clumsy)

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8617dfa6-1348-4a16-93c3-eff3dfca871a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Michael Neale]

That would be preferable if so (in that case you don't want your shell step to error out, yes). 

[Michael Neale]

Right but then without the step failure how can you trap the failure to send the failure email (seems clumsy to have to let the step fail, and then record archive results in the exception handler). 

On Tuesday, March 22, 2016 at 2:51:31 PM UTC+11, Andrew Bayer wrote:

[Michael Neale]

OK sorry for the confusion, 

but you should be able to do what you do (so it doesn't fail on the sh step, but then marks the build as UNSTABLE in the junit archive step).

Then currentBuild.result should have the current build status (or another item in currentBuild, sorry am not sure). 

[Robert Sandell]

Pro tip, requires some "custom whitelisting":

AbstractTestResultAction testResultAction = currentBuild.rawBuild.getAction(AbstractTestResultAction.class)
if (testResultAction != null) {
   echo "Tests: ${testResultAction.failCount} ${testResultAction.failureDiffString} failures of ${testResultAction.totalCount}.\n\n"
}

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/26c5a998-58e2-423b-bc53-8fae37399207%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Robert Sandell

Software Engineer

CloudBees Inc.

[domi]

Thanks!

For now I go with this (I hate whitelisting...):

    if(currentBuild.result != null && !"SUCCESS".equals(currentBuild.result)) {

        ...

    }

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS38jF3XSveXTp_J2KW3UYF5YnsNuACfVAg235PQpBuc1g%40mail.gmail.com.

[Jesse Glick]

On Tue, Mar 22, 2016 at 4:47 AM, domi <do...@fortysix.ch> wrote:
> if(currentBuild.result != null &&
> !"SUCCESS".equals(currentBuild.result)) {
> ...
> }

Yes that is the current recommendation.