Why Post-build actions in Jenkins? - Purpose & Use Cases

The Big Idea

What if your build could clean up and notify your team all by itself?

The Scenario

Imagine you finish building your software manually, then you have to remember to send emails, archive files, and deploy the app all by yourself.

The Problem

This manual way is slow and easy to forget steps. You might miss sending notifications or forget to save important files, causing delays and mistakes.

The Solution

Post-build actions let Jenkins do these follow-up tasks automatically after building. It saves time and ensures nothing is missed.

Before vs After

✗ Before

Build project
Send email
Archive artifacts
Deploy app

✓ After

Build project
-- Post-build actions --
Send email
Archive artifacts
Deploy app

What It Enables

It makes your build process smooth and reliable by automating all the important next steps.

Real Life Example

After a successful build, Jenkins automatically sends a success email to the team and deploys the new version to the test server without anyone lifting a finger.

Key Takeaways

Manual follow-up tasks are slow and error-prone.

Post-build actions automate these tasks right after building.

This ensures faster, consistent, and reliable software delivery.

Practice

1. What is the main purpose of Post-build actions in Jenkins?

easy

A. To start the build process

B. To write the build script

C. To perform tasks automatically after the build finishes

D. To configure the Jenkins server settings

Solution

1. Step 1: Understand Jenkins build phases

   Jenkins runs build steps first, then post-build actions after the build ends.

2. Step 2: Identify the role of post-build actions

   Post-build actions automate tasks like notifications, archiving, or cleanup after the build completes.

3. Final Answer:

   To perform tasks automatically after the build finishes -> Option C

4. Quick Check:

   Post-build actions = tasks after build [OK]

Hint: Post-build actions run after build ends to automate tasks [OK]

Common Mistakes:

• Confusing post-build actions with build steps
• Thinking post-build actions start the build
• Assuming post-build actions configure Jenkins server

2. Which of the following is the correct syntax to add a post-build action in a Jenkins pipeline script?

easy

A. build {
post {
echo 'Build finished'
}
}

B. pipeline {
postbuild {
echo 'Build finished'
}
}

C. steps {
post {
echo 'Build finished'
}
}

D. post {
always {
echo 'Build finished'
}
}

Solution

1. Step 1: Recall Jenkins pipeline post syntax

   In declarative pipelines, post block defines post-build actions with conditions like always.

2. Step 2: Match syntax options

   post { always { echo 'Build finished' } } uses correct post { always { ... } } syntax. Others use invalid blocks like build or postbuild.

3. Final Answer:

   post { always { echo 'Build finished' } } -> Option D

4. Quick Check:

   Post block syntax = post { always { echo 'Build finished' } } [OK]

Hint: Use 'post { always { ... } }' for post-build actions in pipeline [OK]

Common Mistakes:

• Using 'postbuild' instead of 'post'
• Placing post block inside 'steps'
• Using 'build' block incorrectly

3. Given this Jenkins pipeline snippet, what will be printed after the build finishes successfully?

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

medium

A. Building...
Build failed!

B. Building...
Build succeeded!

C. Build succeeded!

D. Build failed!

Solution

1. Step 1: Analyze build steps

   The pipeline prints 'Building...' during the build stage.

2. Step 2: Check post-build actions on success

   On successful build, the success block runs, printing 'Build succeeded!'.

3. Final Answer:

   Building... Build succeeded! -> Option B

4. Quick Check:

   Success post block runs after build [OK]

Hint: Success block runs only if build succeeds [OK]

Common Mistakes:

• Confusing failure block with success block
• Ignoring initial build echo
• Assuming post block runs before build

4. You wrote this Jenkins pipeline post section but the notification never sends on build failure:

post {
  failure {
    mail(to: '[e-mail]', subject: 'Build Failed')
  }
}

What is the likely problem?

medium

A. The mail step requires proper Jenkins email configuration

B. The failure block should be inside steps

C. The mail step requires a steps block inside failure

D. The post block must be inside steps

Solution

1. Step 1: Understand the mail step requirements

   The mail step requires the 'Email Extension Plugin' to be installed and SMTP server configured in Manage Jenkins > Configure System > Extended E-mail Notification.

2. Step 2: Identify the likely problem

   Without proper email configuration (SMTP host, port, credentials, etc.), the notification won't send even if the syntax is correct.

3. Final Answer:

   The mail step requires proper Jenkins email configuration -> Option A

4. Quick Check:

   Mail needs SMTP config [OK]

Hint: Configure SMTP in Jenkins for mail step [OK]

Common Mistakes:

• Not installing Email Extension plugin
• Not setting SMTP server details
• Missing 'from' address or credentials

5. You want to archive build artifacts only if the build succeeds and always send a notification email regardless of build result. Which Jenkins pipeline post section correctly implements this?

hard

A. post {
success {
archiveArtifacts 'build/*.jar'
}
always {
mail(to: '[e-mail]', subject: 'Build Notification')
}
}

B. post {
always {
archiveArtifacts 'build/*.jar'
mail(to: '[e-mail]', subject: 'Build Notification')
}
}

C. post {
success {
archiveArtifacts 'build/*.jar'
mail(to: '[e-mail]', subject: 'Build Notification')
}
}

D. post {
failure {
archiveArtifacts 'build/*.jar'
}
always {
mail(to: '[e-mail]', subject: 'Build Notification')
}
}

Solution

1. Step 1: Identify conditions for each action

   Archiving should happen only on success, so it goes inside success. Email should always send, so it goes inside always.

2. Step 2: Match options with conditions

   post { success { archiveArtifacts 'build/*.jar' } always { mail(to: '[e-mail]', subject: 'Build Notification') } } correctly separates archive in success and mail in always. Others mix conditions incorrectly.

3. Final Answer:

   post { success { archiveArtifacts 'build/*.jar' } always { mail(to: '[e-mail]', subject: 'Build Notification') } } -> Option A

4. Quick Check:

   Use success for archive, always for mail [OK]

Hint: Use 'success' for archive, 'always' for notifications [OK]

Common Mistakes:

• Putting archive in always block
• Sending mail only on success
• Archiving on failure instead of success