currentBuild variables in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to get the current build number.

Jenkins

def buildNumber = currentBuild.[1]

Drag options to blanks, or click blank then click option'

Anumber

Bstatus

Cresult

Dduration

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'result' instead of 'number' returns the build status, not the number.

Using 'duration' gives the build time, not the build number.

The currentBuild.number variable holds the current build number in Jenkins pipelines.

2fill in blank

medium

Complete the code to get the current build result status.

Jenkins

def buildStatus = currentBuild.[1]

Drag options to blanks, or click blank then click option'

Aresult

Bnumber

Cduration

DdisplayName

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'number' returns the build number, not the status.

Using 'duration' returns the build time, not the status.

The currentBuild.result variable holds the status of the current build, such as 'SUCCESS' or 'FAILURE'.

3fill in blank

hard

Fix the error in the code to get the build duration in milliseconds.

Jenkins

def buildTime = currentBuild.[1]

Drag options to blanks, or click blank then click option'

AdurationString

Bduration

Ctime

Delapsed

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'durationString' returns a formatted string, not milliseconds.

Using 'time' or 'elapsed' are not valid properties.

The currentBuild.duration property returns the build duration in milliseconds.

4fill in blank

hard

Fill both blanks to get the build display name and the build result.

Jenkins

def name = currentBuild.[1]
def status = currentBuild.[2]

Drag options to blanks, or click blank then click option'

AdisplayName

Bresult

Cnumber

Dduration

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing 'number' with 'result' instead of 'displayName' and 'result'.

Using 'duration' instead of 'result' for status.

currentBuild.displayName gives the build's display name, and currentBuild.result gives the build status.

5fill in blank

hard

Fill all three blanks to get the build number, duration, and result.

Jenkins

def num = currentBuild.[1]
def time = currentBuild.[2]
def res = currentBuild.[3]

Drag options to blanks, or click blank then click option'

AdisplayName

Bduration

Cresult

Dnumber

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing 'displayName' with 'number' for the build number.

Using 'result' for duration or number.

currentBuild.number is the build number, currentBuild.duration is the build time in milliseconds, and currentBuild.result is the build status.

Practice

1. What does the currentBuild.number variable represent in a Jenkins Pipeline?

easy

A. The number of failed tests in the build

B. The unique build number of the current running job

C. The number of parallel stages in the pipeline

D. The total number of builds ever run on Jenkins

Solution

1. Step 1: Understand the role of currentBuild

   The currentBuild variable holds information about the current Jenkins job execution.

2. Step 2: Identify what number means

   The number property specifically gives the unique build number assigned to this run.

3. Final Answer:

   The unique build number of the current running job -> Option B

4. Quick Check:

   currentBuild.number = build number [OK]

Hint: Remember: currentBuild.number is the build's unique ID [OK]

Common Mistakes:

• Confusing build number with total builds
• Thinking it counts test failures
• Mixing it with stage counts

2. Which of the following is the correct way to access the current build's result status in a Jenkins Pipeline script?

easy

A. currentBuild.result

B. currentBuild.status

C. currentBuild.state

D. currentBuild.outcome

Solution

1. Step 1: Recall the property for build result

   The Jenkins currentBuild object uses result to store the build status like SUCCESS or FAILURE.

2. Step 2: Verify other options

   status, state, and outcome are not valid properties for currentBuild.

3. Final Answer:

   currentBuild.result -> Option A

4. Quick Check:

   Build status = currentBuild.result [OK]

Hint: Use currentBuild.result for build status, not status or state [OK]

Common Mistakes:

• Using currentBuild.status which is undefined
• Confusing result with outcome
• Trying to access non-existent properties

3. Given this Jenkins Pipeline snippet:

echo "Build number: ${currentBuild.number}"
echo "Build status: ${currentBuild.result}"

If the build number is 42 and the build just finished successfully, what will be the output?

medium

A. Build number: 42
Build status: SUCCESS

B. Build number: 42
Build status: null

C. Build number: null
Build status: SUCCESS

D. Build number: 0
Build status: FAILURE

Solution

1. Step 1: Understand variable values after build

   After a successful build, currentBuild.number is the build number (42), and currentBuild.result is "SUCCESS".

2. Step 2: Substitute variables in echo statements

   Replacing variables gives:
   Build number: 42
   Build status: SUCCESS

3. Final Answer:

   Build number: 42 Build status: SUCCESS -> Option A

4. Quick Check:

   Number=42, Result=SUCCESS [OK]

Hint: After success, currentBuild.result = SUCCESS, number = build ID [OK]

Common Mistakes:

• Expecting result to be null before build ends
• Confusing build number with zero
• Assuming result is FAILURE by default

4. You wrote this Jenkins Pipeline snippet:

if (currentBuild.status == 'SUCCESS') {
  echo 'Build succeeded'
} else {
  echo 'Build failed'
}

But it always prints 'Build failed' even when the build succeeds. What is the issue?

medium

A. The string comparison should use == instead of =

B. The if statement needs parentheses around the condition

C. The echo command is incorrect syntax

D. The property should be currentBuild.result, not currentBuild.status

Solution

1. Step 1: Identify the incorrect property usage

   The currentBuild object does not have a status property; the correct property for build result is result.

2. Step 2: Understand why the condition fails

   Since currentBuild.status is undefined, the condition never matches 'SUCCESS', so it always goes to else.

3. Final Answer:

   The property should be currentBuild.result, not currentBuild.status -> Option D

4. Quick Check:

   Use currentBuild.result for status check [OK]

Hint: Use currentBuild.result, not currentBuild.status, for build status [OK]

Common Mistakes:

• Using currentBuild.status instead of currentBuild.result
• Confusing assignment (=) with comparison (==)
• Incorrect echo syntax in Jenkinsfile

5. In a Jenkins Pipeline, you want to set the display name of the current build to include the build number and status, like "Build #42 - SUCCESS". Which snippet correctly does this?

hard

A. currentBuild.displayName = "Build #${build.number} - ${build.result}"

B. currentBuild.name = "Build #${currentBuild.number} - ${currentBuild.status}"

C. currentBuild.displayName = "Build #${currentBuild.number} - ${currentBuild.result}"

D. currentBuild.setDisplayName("Build #${currentBuild.number} - ${currentBuild.result}")

Solution

1. Step 1: Identify the correct property to set display name

   The property to set the build's display name is currentBuild.displayName.

2. Step 2: Use correct variable names and syntax

   Use currentBuild.number and currentBuild.result inside the string with Groovy string interpolation.

3. Final Answer:

   currentBuild.displayName = "Build #${currentBuild.number} - ${currentBuild.result}" -> Option C

4. Quick Check:

   Set displayName with currentBuild.displayName and correct variables [OK]

Hint: Set displayName with currentBuild.displayName and correct variables [OK]

Common Mistakes:

• Using currentBuild.name instead of displayName
• Using undefined variable 'build'
• Trying to call setDisplayName() which doesn't exist