sending email for unstable builds

[Faad Sayaou]

Hi everyone

I am using the extended email plugin for notification when the build fails by using try catch. I will also like to send email when the build is unstable. Below is the structure of my pipeline 

node {
       
   try 
   {
 
    stage('Checkout') {
            cleanWs()
            checkout scm

        }


        stage('Restore') {

            sh "dotnet restore  $proj"

       }

        stage('Build') {
            sh "dotnet restore  $proj"

       }
        stage ('Unit test') {

           sh "dotnet test  $test"
       } 
   }
} catch (err) {
     emailext body: 
            ' ${JOB_NAME} ${BUILD_NUMBER} is failing! Somebody should do something about that. https://jenkins-ma.com/job/Test/${BUILD_NUMBER}/console', subject: 'FAILURE', to: 'someEmail..'
    }

I will like to send not only when the pipeline fails but when the build is unstable. thanks

[Sagar Utekar]

You can check the status of build by using BUILD_STATUS, if it is unstable then send a mail

--
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 jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2c7db49d-68ef-4c41-8cd2-39ff6855ad83%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Simon Bayer]

Dear Faad, dear Sagar,

U could check the global variable  'currentBuild.currentResult' in e.g. post build actions. Maybe it suits your needs. Doks: https://opensource.triology.de/jenkins/pipeline-syntax/globals#currentBuild

Best regards

-------- Ursprüngliche Nachricht --------

Von: Sagar Utekar <sagar....@gslab.com>

Datum: 01.03.19 03:06 (GMT+01:00)

An: jenkins...@googlegroups.com

Betreff: Re: sending email for unstable builds

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANYh6tf5h6_LAafRrKLROquy3mO95puNkbMY0%3DATh5uRnkXeyw%40mail.gmail.com.

[Simon Bayer]

Check This if u need post build actions for different build status: https://jenkins.io/doc/pipeline/tour/post/

-------- Ursprüngliche Nachricht --------

Von: Simon Bayer <sch...@msn.com>

Datum: 01.03.19 06:32 (GMT+01:00)

[Faad Sayaou]

thanks @Simon and @Sagar for your responses.  'currentBuild.currentResult' is definitely what i needed and works as intended. 

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/DM6PR15MB3452B3FF105E05324B50A9C4AC760%40DM6PR15MB3452.namprd15.prod.outlook.com.

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

--

Best Regards / Mit freundlichen Grüßen,

Faad Sayaou,

Embedded Systems for Mechatronics Masters student | FH Dortmund | Germany

Fachhochschule Dortmund

University of Applied Sciences and Arts

Email: faad...@gmail.com

[Simon Bayer]

Vers Nice, appreciate your feedback. Glad that We could help you :)

-------- Ursprüngliche Nachricht --------

Von: Faad Sayaou <faa...@gmail.com>

Datum: 01.03.19 08:34 (GMT+01:00)

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAL2KjjQ-6Q66229-Zh-5BRYtMvRANN-dmOZCwteJ7Re9n%3D1Tcw%40mail.gmail.com.

[Mark Lübbehüsen]

Hi,

its better you send emails in the post action

post {

      always {

           

}

        success {

        }

        unstable {

        

}

        failure {

           

}

aborted {

}

    }

https://jenkins.io/doc/pipeline/tour/post/

[Faad Sayaou]

thanks for your contribution. Is there any other way of failing of failing the pipeline when unit test stage is unstable? I have something like the following in my code to ignore the failed test but I will like to stop the pipeline and publish unit test result.

I am currently experiencing a strange effect when using the MStest plugin. My test report is only generated when the test is successful but when it fails, no test report is generated. 

node {

        stage('Checkout') {
            cleanWs()
            checkout scm

            return
            skipRemainingStages = true
        }


        stage('Restore') {

            sh "dotnet restore  $proj"

        }

        stage('Build') {
            sh "dotnet publish $proj --output $outputFolder --configuration Release -p:Version=$buildVersion -p:FileVersion=$buildVersion"

       }
        stage ('Unit test') {

               sh  "dotnet restore $UnitTest"
               sh returnStdout: true, script: "dotnet test $UnitTest --logger \'trx;LogFileName=unit_tests.xml\' || true"

               step ([$class: 'MSTestPublisher', testResultsFile:"**/*.xml", failOnError: true, keepLongStdio: true])

        } 

         stage ('publish') {
        }
 }

I do not want to publish when the build is unstable. Like I mentioned earlier. I want to stop the build and publish test result. I tried using answers suggested above but could not help in my use-case.any idea?

[Mark Lübbehüsen]

script {

                currentBuild.result = currentBuild.result ?: 'FAILED'

       }

[Mark Lübbehüsen]

HI,

you can fail your pipeline if you put the following code in the unit test stage

script {

                currentBuild.result = currentBuild.result ?: 'FAILED'

          } 

Am Dienstag, 12. März 2019 23:31:43 UTC+1 schrieb Faad Sayaou:

[Aaron Digulla]

Hi,

I'm using this code:

    node(...) {
        try {
            ...add stages here...
        } catch(Exception e) {
            currentBuild.result = 'FAILURE' // Let the post step know that the build failed with an error.
            throw e
        } finally {
            builder.post(currentBuild)
        }
     } // node

The code for post() looks like so:

    def post(def currentBuild) {
        String currentResult = currentBuild.result ?: 'SUCCESS'
        echo "post ${currentResult}"
       
        try {
            postAlways(currentBuild)
        } catch(Exception e) {
            def converted = toString(e)
            echo "postAlways failed (ignored):\n${converted}"
        }
       
        if (currentResult == 'SUCCESS') {
            success(currentBuild)
        } else {
            failed(currentBuild, currentResult)
        }
    }

Hope this helps,

Aaron Digulla