currentBuild variables in Jenkins - Step-by-Step Execution

Process Flow - currentBuild variables

Start Build

↓

Initialize currentBuild

↓

Set Variables: result, duration, displayName, etc.

↓

Pipeline Steps Execute

↓

Update currentBuild Variables

↓

Access currentBuild Variables in Script

↓

Use Variables for Logic or Reporting

↓

Build Ends

The currentBuild object is created at build start, holds info like status and duration, updates during the build, and can be accessed anytime in the pipeline.

Execution Sample

Jenkins

pipeline {
  agent any
  stages {
    stage('Example') {
      steps {
        script {
          echo "Build status: ${currentBuild.currentResult}"
        }
      }
    }
  }
}

This pipeline prints the current build status using currentBuild.currentResult.

Process Table

Step	Action	currentBuild Variable	Value	Notes
1	Build starts	result	null	No result yet
2	Stage 'Example' starts	result	null	Build running
3	Inside script block	currentResult	SUCCESS	Default before failure
4	Stage completes	result	SUCCESS	Stage passed
5	Build completes	result	SUCCESS	Build finished successfully
6	Access displayName	displayName	#1	Build number shown
7	Access duration	duration	5000	Duration in ms (example)
8	Build ends	result	SUCCESS	Pipeline finished
9	Exit	-	-	Build complete, no more updates

💡 Build finishes, currentBuild variables hold final build info.

Status Tracker

Variable	Start	After Step 3	After Step 5	After Step 8
result	null	SUCCESS	SUCCESS	SUCCESS
currentResult	null	SUCCESS	SUCCESS	SUCCESS
displayName	null	#1	#1	#1
duration	null	null	5000	5000

Key Moments - 3 Insights

Why is currentBuild.result null at the start but currentBuild.currentResult shows SUCCESS inside the script?

At build start, result is not set yet (null). currentResult reflects the current known status during execution, often defaulting to SUCCESS until a failure occurs, as shown in execution_table row 3.

Can currentBuild variables be changed manually in the pipeline?

Yes, some variables like currentBuild.displayName can be set manually to customize build names, but others like duration are updated automatically by Jenkins, as seen in execution_table rows 6 and 7.

What happens to currentBuild variables after the build finishes?

They hold the final build state and info for reporting or downstream steps, as shown in execution_table rows 8 and 9.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of currentBuild.result at step 2?

A null

B SUCCESS

C FAILURE

D UNKNOWN

💡 Hint

Check the 'currentBuild Variable' and 'Value' columns at step 2 in the execution_table.

At which step does currentBuild.duration get a value?

A Step 5

B Step 7

C Step 3

D Step 9

💡 Hint

Look for 'duration' variable updates in the execution_table rows.

If the build failed at step 5, what would currentBuild.result likely be?

A SUCCESS

B null

C FAILURE

D ABORTED

💡 Hint

Consider what currentBuild.result represents after stage completion in the execution_table.

Concept Snapshot

currentBuild is a Jenkins pipeline object holding build info.
Key variables: result (final status), currentResult (live status), displayName (build label), duration (build time).
result starts null, updates as build progresses.
Use currentBuild variables in scripts to check or set build info.
Useful for conditional logic and reporting in pipelines.

Full Transcript

The currentBuild object in Jenkins pipelines tracks the build's status and details. It starts empty at build start, then updates variables like result, currentResult, displayName, and duration as the build runs. For example, currentBuild.result is null initially but becomes SUCCESS if the build passes. You can access these variables inside script blocks to make decisions or print info. Some variables like displayName can be set manually to customize the build label. After the build finishes, currentBuild variables hold the final state for reporting or further steps. This visual trace shows how these variables change step-by-step during a simple pipeline.