Post section (success, failure, always) in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output when the post { success } block runs?

Consider this Jenkins pipeline snippet:

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        echo 'Building...'
      }
    }
  }
  post {
    success {
      echo 'Build succeeded!'
    }
  }
}

What will Jenkins print if the build stage completes without errors?

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        echo 'Building...'
      }
    }
  }
  post {
    success {
      echo 'Build succeeded!'
    }
  }
}

A Building...\nBuild succeeded!

B Build succeeded!\nBuilding...

C Building...

D No output, post block does not run

💡 Hint

Remember, the post { success } block runs only if the build succeeds.

The echo 'Building...' runs during the build stage. After successful completion, the post { success } block runs and prints 'Build succeeded!'. So output is both lines in order.

💻 Command Output

intermediate

What happens when the post { failure } block is triggered?

Given this Jenkins pipeline:

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        sh 'exit 1'
      }
    }
  }
  post {
    failure {
      echo 'Tests failed!'
    }
  }
}

What will Jenkins output if the shell command fails?

Jenkins

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        sh 'exit 1'
      }
    }
  }
  post {
    failure {
      echo 'Tests failed!'
    }
  }
}

A Tests failed!

B No output, failure block does not run

C Pipeline succeeds without output

D Build succeeded!

💡 Hint

The post { failure } block runs only if any stage fails.

The shell command exits with code 1, causing the stage to fail. The post { failure } block then runs and prints 'Tests failed!'.

🔀 Workflow

advanced

Order the execution of post blocks in this Jenkins pipeline

Given this Jenkins pipeline snippet:

pipeline {
  agent any
  stages {
    stage('Deploy') {
      steps {
        echo 'Deploying...'
      }
    }
  }
  post {
    always {
      echo 'Cleaning up...'
    }
    success {
      echo 'Deployment succeeded!'
    }
    failure {
      echo 'Deployment failed!'
    }
  }
}

What is the correct order of post block execution if the deployment succeeds?

A 1,2,3

B 2,1,3

C 1,3,2

D 2,3,1

💡 Hint

The always block runs after success or failure blocks.

When deployment succeeds, success runs first, then always. The failure block does not run.

❓ Troubleshoot

advanced

Why does the post { always } block not run in this pipeline?

Look at this Jenkins pipeline:

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        error 'Forced failure'
      }
    }
  }
  post {
    always {
      echo 'This should always run'
    }
  }
}

Despite the error, the message in always does not appear. What is the most likely reason?

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        error 'Forced failure'
      }
    }
  }
  post {
    always {
      echo 'This should always run'
    }
  }
}

A The <code>post</code> block is misplaced outside the pipeline block

B The <code>error</code> step stops the entire Jenkins server

C The <code>always</code> block only runs on success

D The pipeline is scripted, but <code>post</code> is only for declarative pipelines

💡 Hint

Check if the pipeline syntax matches the post block usage.

The post section is valid only in declarative pipelines. If the pipeline is scripted, post blocks do not run.

✅ Best Practice

expert

Which post block usage ensures cleanup regardless of build result?

You want to delete temporary files after every build, no matter if it succeeds or fails. Which Jenkins post block snippet achieves this best?

post {
  A) success {
       sh 'rm -rf temp/'
     }
  B) failure {
       sh 'rm -rf temp/'
     }
  C) always {
       sh 'rm -rf temp/'
     }
  D) changed {
       sh 'rm -rf temp/'
     }
}

A Runs only if build succeeds, so may skip cleanup on failure

B Runs only if build fails, so may skip cleanup on success

C Runs after every build, ensuring cleanup always

D Runs only if build status changes, may skip some builds

💡 Hint

Think about which post condition always runs regardless of build outcome.

The always block runs after every build, success or failure, making it ideal for cleanup tasks.