How to implement Post-Build stage using Jenkins Pipeline plug-in? How to implement Post-Build stage using Jenkins Pipeline plug-in? jenkins jenkins

How to implement Post-Build stage using Jenkins Pipeline plug-in?


The best way is to use post build action in the pipeline script.

Handling Failures
Declarative Pipeline supports robust failure handling by default via its post section which allows declaring a number of different "post conditions" such as: always, unstable, success, failure, and changed. The Pipeline Syntax section provides more detail on how to use the various post conditions.

Jenkinsfile (Declarative Pipeline)

pipeline {    agent any    stages {        stage('Test') {            steps {                sh 'make check'            }        }    }    post {        always {            junit '**/target/*.xml'        }        failure {            mail to: team@example.com, subject: 'The Pipeline failed :('        }    }}

The documentation is belowhttps://jenkins.io/doc/book/pipeline/syntax/#post


If you are using try/catch and you want a build to be marked as unstable or failed then you must use currentBuild.result = 'UNSTABLE' etc. I believe some plugins like the JUnit Report plugin will set this for you if it finds failed tests in the junit results. But in most cases you have to set it your self if you are catching errors.

The second option if you don't want to continue is to rethrow the error.

stage 'build'... buildtry {    ... tests} catch(err) {    //do something then re-throw error if needed.    throw(err)}stage 'post-build'...


FWIW, if you are using scripted pipelines and not declarative, you should use a try/catch/finally block as suggested in the other answers. In the finally block, if you want to mimic what the declarative pipeline does, you can either put the following directly in the block, or make it a function and call that function from your finally block:

def currResult = currentBuild.result ?: 'SUCCESS'def prevResult = currentBuild.previousBuild?.result ?: 'NOT_BUILT'// Identify current resultboolean isAborted = (currResult == 'ABORTED')boolean isFailure = (currResult == 'FAILURE')boolean isSuccess = (currResult == 'SUCCESS')boolean isUnstable = (currResult == 'UNSTABLE')boolean isChanged = (currResult != prevResult)boolean isFixed = isChanged && isSuccess && (prevResult != 'ABORTED') && (prevResult != 'NOT_BUILT')boolean isRegression = isChanged && currentBuild.resultIsWorseOrEqualTo(prevResult)onAlways()if (isChanged) {    onChanged()    if (isFixed) {        onFixed()    } else if (isRegression) {        onRegression()    }}if (isSuccess) {    onSuccess()} else {    if (isAborted) {        onAborted()    }    onUnsuccessful()    if (isFailure) {        onFailure()    }    if (isUnstable) {        onUnstable()    }}onCleanup()

The various onXYZ() calls are functions that you would define to handle that particular condition instead of using the nicer syntax of the declarative post blocks.