Build status badges in Jenkins - Step-by-Step Execution

Process Flow - Build status badges

Start Jenkins Job

↓

Job Runs Build

↓

Build Passes or Fails

↓

Update Badge Status

↓

Badge URL Shows Status

↓

Users See Badge on README or Dashboard

The Jenkins job runs a build, updates the badge status based on success or failure, and the badge URL reflects this status for users.

Execution Sample

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        sh 'make build'
      }
    }
  }
  post {
    success {
      script {
        currentBuild.description = "![Build Status](https://img.shields.io/badge/build-passing-brightgreen)"
      }
    }
    failure {
      script {
        currentBuild.description = "![Build Status](https://img.shields.io/badge/build-failing-red)"
      }
    }
  }
}

This Jenkins pipeline runs a build and sets a badge URL in the build description showing pass or fail status.

Process Table

Step	Action	Build Result	Badge URL	User View
1	Start Jenkins Job	N/A	N/A	No badge yet
2	Run 'make build'	Running	N/A	No badge yet
3	Build completes successfully	Success	https://img.shields.io/badge/build-passing-brightgreen	Green passing badge shown
4	Set build description with passing badge	Success	https://img.shields.io/badge/build-passing-brightgreen	Green passing badge shown
5	User views README or dashboard	Success	https://img.shields.io/badge/build-passing-brightgreen	Green passing badge visible
6	If build fails instead	Failure	https://img.shields.io/badge/build-failing-red	Red failing badge shown
7	Set build description with failing badge	Failure	https://img.shields.io/badge/build-failing-red	Red failing badge shown
8	User views README or dashboard	Failure	https://img.shields.io/badge/build-failing-red	Red failing badge visible

💡 Build finishes with success or failure, badge URL updated accordingly, user sees badge status.

Status Tracker

Variable	Start	After Build Success	After Build Failure
currentBuild.description	null		

Key Moments - 2 Insights

Why does the badge URL change after the build finishes?

Because the Jenkins pipeline updates currentBuild.description in the post section depending on success or failure, as shown in execution_table rows 4 and 7.

Can the badge show status before the build finishes?

No, the badge URL is set only after the build completes, so before that it is not available, as seen in execution_table rows 1 and 2.

Visual Quiz - 3 Questions

Look at the execution_table at step 3, what is the build result and badge URL?

A Build Result: Running, Badge URL: N/A

B Build Result: Success, Badge URL: https://img.shields.io/badge/build-passing-brightgreen

C Build Result: Failure, Badge URL: https://img.shields.io/badge/build-failing-red

D Build Result: Success, Badge URL: N/A

💡 Hint

Check row 3 in execution_table for build result and badge URL after build success.

At which step does the user first see the badge on the dashboard?

A Step 2

B Step 4

C Step 5

D Step 1

💡 Hint

Look at execution_table rows where User View column shows badge visibility.

If the build fails, what will currentBuild.description be set to?

A 

B 

C null

D No change

💡 Hint

Check variable_tracker for currentBuild.description after build failure.

Concept Snapshot

Build status badges show if a Jenkins build passed or failed.
Use pipeline post blocks to set badge URLs.
Badge URLs use services like shields.io.
Users see badges on README or dashboards.
Badge updates only after build finishes.

Full Transcript

This visual execution shows how Jenkins builds update a build status badge. The pipeline runs a build command. After the build finishes, the pipeline sets the build description to a badge URL. If the build succeeds, the badge is green and says passing. If it fails, the badge is red and says failing. Users see the badge on project pages or dashboards. The badge updates only after the build completes, never before. Variables like currentBuild.description hold the badge URL and change after build success or failure.