WithCredentials block usage in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to use the credentials ID inside the withCredentials block.

Jenkins

withCredentials([usernamePassword(credentialsId: '[1]', usernameVariable: 'USER', passwordVariable: 'PASS')]) {
    echo "Username is $USER"
}

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

Asecret123

BcredentialsId

Cuser_pass

Dmy-credentials-id

Attempts:

3 left

💡 Hint

Common Mistakes

Using variable names instead of the actual credentials ID.

Leaving the credentialsId blank.

The credentialsId must be the actual ID of the stored credentials in Jenkins.

2fill in blank

medium

Complete the code to use a secret text credential inside the withCredentials block.

Jenkins

withCredentials([string(credentialsId: '[1]', variable: 'TOKEN')]) {
    sh 'echo $TOKEN'
}

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

Atoken-secret

Buser-pass

Cmy-password

Dapi-key

Attempts:

3 left

💡 Hint

Common Mistakes

Using a usernamePassword ID for a secret text block.

Using the wrong variable name.

The credentialsId must match the ID of the secret text credential stored in Jenkins.

3fill in blank

hard

Fix the error in the withCredentials block to correctly bind the username and password.

Jenkins

withCredentials([usernamePassword(credentialsId: 'cred-id', usernameVariable: '[1]', passwordVariable: 'PASS')]) {
    echo "User is $USER"
}

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

AUSERNAME

BUSER

Cuser

Dusername

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different case for the variable name.

Mismatching variable names between declaration and usage.

The variable name USER matches the usage inside the block $USER.

4fill in blank

hard

Fill both blanks to correctly use multiple credentials inside the withCredentials block.

Jenkins

withCredentials([usernamePassword(credentialsId: '[1]', usernameVariable: 'USER', passwordVariable: '[2]')]) {
    echo "User: $USER, Password: $PASS"
}

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

Amulti-cred-id

BPASSWORD

CPASS

Duserpass

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong variable names for passwordVariable.

Using incorrect credentialsId.

The credentialsId must be the correct ID, and the passwordVariable must match the variable used inside the block.

5fill in blank

hard

Fill all three blanks to correctly use a file credential inside the withCredentials block.

Jenkins

withCredentials([file(credentialsId: '[1]', variable: '[2]')]) {
    sh 'cat $[3]'
}

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

Afile-cred-id

BFILE_PATH

DfileVar

Attempts:

3 left

💡 Hint

Common Mistakes

Using different variable names in declaration and usage.

Using wrong credentialsId.

The credentialsId is the ID of the file credential. The variable name must be consistent and used inside the shell command.

Practice

1. What is the main purpose of the withCredentials block in a Jenkins pipeline?

easy

A. To display credentials in the console output for debugging

B. To permanently store credentials in the pipeline script

C. To securely inject credentials only inside the block without exposing them elsewhere

D. To create new credentials in Jenkins

Solution

1. Step 1: Understand the purpose of withCredentials

   The block is designed to provide credentials securely only within its scope.

2. Step 2: Analyze other options

   Options A, B, and D describe incorrect or unsafe behaviors not related to withCredentials.

3. Final Answer:

   To securely inject credentials only inside the block without exposing them elsewhere -> Option C

4. Quick Check:

   Secure injection inside block = C [OK]

Hint: Remember: credentials only live inside the block [OK]

Common Mistakes:

• Thinking credentials persist outside the block
• Assuming credentials are printed in logs
• Confusing with credential creation

2. Which of the following is the correct syntax to use a username and password credential with withCredentials in a Jenkins pipeline?

easy

A. withCredentials([usernamePassword(credentialsId: 'cred-id', usernameVariable: 'USER', passwordVariable: 'PASS')]) { ... }

B. withCredentials(usernamePassword('cred-id', 'USER', 'PASS')) { ... }

C. withCredentials { usernamePassword('cred-id', 'USER', 'PASS') ... }

D. withCredentials([usernamePassword('cred-id', 'USER', 'PASS')]) { ... }

Solution

1. Step 1: Recall correct withCredentials syntax

   The correct syntax uses a list with usernamePassword specifying named parameters.

2. Step 2: Check each option

   Only withCredentials([usernamePassword(credentialsId: 'cred-id', usernameVariable: 'USER', passwordVariable: 'PASS')]) { ... } uses named parameters and list syntax correctly; others miss brackets or parameter names.

3. Final Answer:

   withCredentials([usernamePassword(credentialsId: 'cred-id', usernameVariable: 'USER', passwordVariable: 'PASS')]) { ... } -> Option A

4. Quick Check:

   Named params + list = A [OK]

Hint: Use named parameters inside a list for credentials [OK]

Common Mistakes:

• Omitting square brackets around credentials
• Not using named parameters
• Wrong block structure

3. Given this Jenkins pipeline snippet:

withCredentials([string(credentialsId: 'token-id', variable: 'TOKEN')]) {
  sh 'echo $TOKEN'
}

What will happen when this pipeline runs?

medium

A. The token will be printed as plain text in the Jenkins UI

B. The secret token value will be printed in the console output

C. The pipeline will fail because $TOKEN is not accessible

D. The shell command will print the token value but it will be masked in logs

Solution

1. Step 1: Understand withCredentials behavior

   The secret is injected as an environment variable inside the block and Jenkins masks it in logs.

2. Step 2: Analyze the shell command output

   The echo $TOKEN prints the token, but Jenkins hides it in console output to protect secrets.

3. Final Answer:

   The shell command will print the token value but it will be masked in logs -> Option D

4. Quick Check:

   Secrets masked in logs = A [OK]

Hint: Secrets print masked, not visible in logs [OK]

Common Mistakes:

• Assuming secrets print as plain text
• Thinking environment variables are unavailable
• Confusing console output with UI display

4. Identify the error in this Jenkins pipeline snippet:

withCredentials([usernamePassword(credentialsId: 'cred-id', usernameVariable: 'USER')]) {
  sh 'echo $USER $PASS'
}

medium

A. Missing passwordVariable parameter causes $PASS to be undefined

B. Credentials ID is incorrect format

C. The sh step cannot access environment variables

D. The withCredentials block must not use a list

Solution

1. Step 1: Check withCredentials parameters

   The snippet provides only usernameVariable but misses passwordVariable.

2. Step 2: Understand impact on shell command

   Since passwordVariable is missing, $PASS is undefined and will cause an empty or error output.

3. Final Answer:

   Missing passwordVariable parameter causes $PASS to be undefined -> Option A

4. Quick Check:

   Both username and password variables needed = D [OK]

Hint: Always specify both usernameVariable and passwordVariable [OK]

Common Mistakes:

• Forgetting passwordVariable
• Assuming shell can't access env vars
• Wrong credentialsId format

5. You want to use multiple credentials (a username/password and a secret text) inside a Jenkins pipeline securely. Which is the correct way to use withCredentials to access both?

hard

A. withCredentials(usernamePassword(credentialsId: 'cred1', usernameVariable: 'USER', passwordVariable: 'PASS')) {
withCredentials(string(credentialsId: 'cred2', variable: 'TOKEN')) { ... }
}

B. withCredentials([usernamePassword(credentialsId: 'cred1', usernameVariable: 'USER', passwordVariable: 'PASS'), string(credentialsId: 'cred2', variable: 'TOKEN')]) { ... }

C. withCredentials([usernamePassword('cred1', 'USER', 'PASS'), string('cred2', 'TOKEN')]) { ... }

D. withCredentials([usernamePassword(credentialsId: 'cred1', usernameVariable: 'USER', passwordVariable: 'PASS')]) { withCredentials([string(credentialsId: 'cred2', variable: 'TOKEN')]) { ... } }

Solution

1. Step 1: Understand multiple credentials usage

   You can pass multiple credentials as a list inside a single withCredentials block.

2. Step 2: Compare options

   withCredentials([usernamePassword(credentialsId: 'cred1', usernameVariable: 'USER', passwordVariable: 'PASS'), string(credentialsId: 'cred2', variable: 'TOKEN')]) { ... } correctly uses a list with both credential types together. Options A and D nest blocks unnecessarily. withCredentials([usernamePassword('cred1', 'USER', 'PASS'), string('cred2', 'TOKEN')]) { ... } uses wrong syntax.

3. Final Answer:

   withCredentials([usernamePassword(credentialsId: 'cred1', usernameVariable: 'USER', passwordVariable: 'PASS'), string(credentialsId: 'cred2', variable: 'TOKEN')]) { ... } -> Option B

4. Quick Check:

   Multiple creds in one list = B [OK]

Hint: Use one list with all credentials inside withCredentials [OK]

Common Mistakes:

• Nesting multiple withCredentials blocks unnecessarily
• Using incorrect parameter syntax
• Passing credentials without a list