How do I assure that a Jenkins pipeline stage is always executed, even if a previous one failed?

Question

I am looking for a Jenkinsfile example of having a step that is always executed, even if a previous step failed.

I want to assure that I archive some builds results in case of failure and I need to be able to have an always-running step at the end.

How can I achieve this?

I hope this question would be helpful, http://stackoverflow.com/q/36651432/6128602. — luka5z, May 26 '16 at 15:25

score 19 · Answer 1 · answered Mar 09 '18 at 17:45

19

We switched to using Jenkinsfile Declarative Pipelines, which lets us do things like this:

pipeline {
    agent any
    stages {
        stage('Test') {
            steps {
                sh './gradlew check'
            }
        }
    }
    post {
        always {
            junit 'build/reports/**/*.xml'
        }
    }
}

References:

Tests and Artifacts

Jenkins Pipeline Syntax

answered Mar 09 '18 at 17:45

m0j0hn

532
4
16

4

If you use a docker container as an agent, this won't run the post within the container :( – djsumdog Mar 21 '18 at 16:10

score 10 · Answer 2 · answered May 26 '16 at 16:20

10

   try {
         sh "false"
    } finally {

        stage 'finalize'
        echo "I will always run!"
    }

answered May 26 '16 at 16:20

sorin

161,544
178
535
806

how do you do this in a pipeline script? – Andrew Myhre Oct 31 '17 at 18:03
@AndrewMyhre that is pipeline script syntax so you can copypaste that into your pipeline definition. – jjmontes Aug 19 '19 at 16:01

score 1 · Answer 3 · answered Jun 27 '22 at 07:28

Another possibility is to use a parallel section in combination with a lock. For example:

pipeline {
    stages {
        parallel {
            stage('Stage 1') {
                steps {
                    lock('MY_LOCK') {
                        echo 'do stuff 1'
                    }
                }
            }
            stage('Stage 2') {
                steps {
                    lock('MY_LOCK') {
                        echo 'do stuff 2'
                    }
                }
            }
        }
    }
}

Parallel stages in a parallel section only abort other stages in the same parallel section if the fail fast option for the parallel section is set. See the docs.

The order in which these steps will be executed might be random. — M. Niklas, Jul 01 '22 at 08:52
I checked some runs, and they all execute the stages in order of the Jenkinsfile — hintze, Jul 04 '22 at 06:59

score 0 · Answer 4 · answered Mar 28 '23 at 12:36

When a Jenkins stage fails, all of the rest starts and ignore message. So stages are skipped but you really want them to run. You can use the catchError block to catch errors and continue with the pipeline. Here’s an example:

stage('Example') {
    steps {
        catchError(buildResult: 'SUCCESS', stageResult: 'FAILURE') {
            sh './run-my-script.sh'
        }
    }
}

How do I assure that a Jenkins pipeline stage is always executed, even if a previous one failed?

4 Answers4

Linked