Build wrappers in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add a build wrapper that timestamps the console output.

Jenkins

<buildWrappers>
  <[1]/>
</buildWrappers>

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

AansiColor

Btimeout

CcredentialsBinding

Dtimestamps

Attempts:

3 left

💡 Hint

Common Mistakes

Using timeout instead of timestamps.

Confusing ansiColor with timestamping.

The timestamps build wrapper adds timestamps to the console output, helping track when each step runs.

2fill in blank

medium

Complete the code to add a build wrapper that sets a timeout of 10 minutes.

Jenkins

<buildWrappers>
  <[1]>
    <timeoutMinutes>10</timeoutMinutes>
  </[1]>
</buildWrappers>

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

Atimestamps

Btimeout

CansiColor

DcredentialsBinding

Attempts:

3 left

💡 Hint

Common Mistakes

Using timestamps instead of timeout.

Forgetting to close the wrapper tag properly.

The timeout build wrapper stops the build if it runs longer than the specified minutes.

3fill in blank

hard

Fix the error in the build wrapper code to correctly bind credentials.

Jenkins

<buildWrappers>
  <[1]>
    <bindings>
      <usernamePassword>
        <usernameVariable>USER</usernameVariable>
        <passwordVariable>PASS</passwordVariable>
        <credentialsId>my-creds</credentialsId>
      </usernamePassword>
    </bindings>
  </[1]>
</buildWrappers>

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

Atimestamps

Btimeout

CcredentialsBinding

DansiColor

Attempts:

3 left

💡 Hint

Common Mistakes

Using timeout or timestamps instead of credentialsBinding.

Misnaming the wrapper tag.

The credentialsBinding wrapper allows secure use of credentials during the build.

4fill in blank

hard

Fill both blanks to add a build wrapper that colors console output and sets a timeout of 5 minutes.

Jenkins

<buildWrappers>
  <[1]/>
  <[2]>
    <timeoutMinutes>5</timeoutMinutes>
  </[2]>
</buildWrappers>

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

AansiColor

Btimeout

Ctimestamps

DcredentialsBinding

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping the wrapper names.

Forgetting to close tags properly.

The ansiColor wrapper adds color to console output. The timeout wrapper stops the build after 5 minutes.

5fill in blank

hard

Fill all three blanks to add a build wrapper that timestamps output, binds credentials, and sets a timeout of 15 minutes.

Jenkins

<buildWrappers>
  <[1]/>
  <[2]>
    <bindings>
      <usernamePassword>
        <usernameVariable>USER</usernameVariable>
        <passwordVariable>PASS</passwordVariable>
        <credentialsId>admin-creds</credentialsId>
      </usernamePassword>
    </bindings>
  </[2]>
  <[3]>
    <timeoutMinutes>15</timeoutMinutes>
  </[3]>
</buildWrappers>

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

Atimestamps

BcredentialsBinding

Ctimeout

DansiColor

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up wrapper names.

Missing closing tags.

This code adds three wrappers: timestamps for time info, credentialsBinding for secure credentials, and timeout to limit build time.

Practice

1. What is the main purpose of build wrappers in Jenkins?

easy

A. To prepare the environment before a build starts

B. To deploy the application after the build

C. To write test cases for the build

D. To monitor server health during the build

Solution

1. Step 1: Understand build wrappers role

   Build wrappers are used to set up or modify the environment before the build runs.

2. Step 2: Differentiate from other build steps

   Deployment, testing, and monitoring happen after or outside the build wrapper scope.

3. Final Answer:

   To prepare the environment before a build starts -> Option A

4. Quick Check:

   Build wrappers = environment setup [OK]

Hint: Build wrappers run before build steps start [OK]

Common Mistakes:

• Confusing build wrappers with deployment steps
• Thinking build wrappers run after the build
• Assuming build wrappers handle testing

2. Which syntax correctly adds a build wrapper to mask passwords in a Jenkins pipeline?

easy

A. properties { buildWrappers { maskPasswords() } }

B. properties { buildWrappers { mask_passwords() } }

C. buildWrappers { properties { maskPasswords() } }

D. buildWrappers { maskPasswords() }

Solution

1. Step 1: Recall correct Jenkins pipeline syntax

   Build wrappers are added inside the properties block using buildWrappers { maskPasswords() }.

2. Step 2: Identify syntax errors in options

   properties { buildWrappers { mask_passwords() } } uses underscores which is incorrect. Options C and D misplace the blocks.

3. Final Answer:

   properties { buildWrappers { maskPasswords() } } -> Option A

4. Quick Check:

   Correct syntax = properties + buildWrappers + maskPasswords [OK]

Hint: Use properties block then buildWrappers inside [OK]

Common Mistakes:

• Using underscores instead of camelCase
• Placing buildWrappers outside properties block
• Omitting properties block entirely

3. Given this Jenkins pipeline snippet, what will happen before the build runs?

properties {
  buildWrappers {
    timeout(time: 10, unit: 'MINUTES')
  }
}

medium

A. Passwords will be masked in the console output

B. The build workspace will be cleaned before starting

C. The build will be aborted if it runs longer than 10 minutes

D. The build will run without any timeout

Solution

1. Step 1: Understand the timeout build wrapper

   The timeout wrapper aborts the build if it exceeds the specified time.

2. Step 2: Match the behavior to options

   The build will be aborted if it runs longer than 10 minutes correctly describes the timeout effect. Other options describe different wrappers.

3. Final Answer:

   The build will be aborted if it runs longer than 10 minutes -> Option C

4. Quick Check:

   timeout wrapper = abort after time limit [OK]

Hint: Timeout wrapper stops build after set minutes [OK]

Common Mistakes:

• Confusing timeout with workspace cleanup
• Assuming masking passwords happens automatically
• Ignoring the timeout setting effect

4. You added this build wrapper in your Jenkins pipeline but it does not mask passwords as expected:

properties {
  buildWrappers {
    maskpasswords()
  }
}

What is the likely problem?

medium

A. maskPasswords() requires parameters

B. Build wrappers cannot mask passwords

C. The properties block is missing

D. The function name should be camelCase: maskPasswords()

Solution

1. Step 1: Check function name spelling and case

   The correct function name is maskPasswords() with capital P, not maskpasswords().

2. Step 2: Verify other syntax parts

   The properties block is present, and maskPasswords does not require parameters.

3. Final Answer:

   The function name should be camelCase: maskPasswords() -> Option D

4. Quick Check:

   Function names are case-sensitive in Jenkins [OK]

Hint: Check exact camelCase spelling for build wrappers [OK]

Common Mistakes:

• Using wrong case in function names
• Assuming build wrappers need parameters always
• Removing properties block accidentally

5. You want to ensure your Jenkins build cleans the workspace and aborts if it runs over 15 minutes. Which build wrappers configuration achieves this?

hard

A. properties {
buildWrappers {
timeout(time: 15, unit: 'MINUTES')
cleanWs()
}
}

B. properties {
buildWrappers {
cleanWs()
timeout(time: 15, unit: 'MINUTES')
}
}

C. buildWrappers {
cleanWs()
timeout(time: 15, unit: 'MINUTES')
}

D. properties {
cleanWs()
timeout(time: 15, unit: 'MINUTES')
}

Solution

1. Step 1: Confirm correct placement inside properties block

   Build wrappers must be inside properties { buildWrappers { ... } } to work properly.

2. Step 2: Verify both wrappers are included

   properties { buildWrappers { cleanWs() timeout(time: 15, unit: 'MINUTES') } } includes cleanWs() and timeout() inside buildWrappers correctly.

3. Step 3: Eliminate incorrect options

   properties { buildWrappers { timeout(time: 15, unit: 'MINUTES') cleanWs() } } has incorrect order but is syntactically valid; however, the question implies the order in B is preferred. Options C and D have incorrect block structure.

4. Final Answer:

   properties { buildWrappers { cleanWs() timeout(time: 15, unit: 'MINUTES') } } -> Option B

5. Quick Check:

   Both cleanWs and timeout inside properties/buildWrappers [OK]

Hint: Put all wrappers inside properties { buildWrappers { ... } } [OK]

Common Mistakes:

• Placing wrappers outside properties block
• Omitting one of the required wrappers
• Incorrect syntax for buildWrappers block