WithCredentials block usage in Jenkins - Step-by-Step Execution

Process Flow - WithCredentials block usage

Start Pipeline

↓

Enter withCredentials block

↓

Credentials injected as env vars

↓

Use credentials inside block

↓

Exit withCredentials block

↓

Credentials removed from env

↓

Continue pipeline

The pipeline starts, enters the withCredentials block where credentials are injected as environment variables, uses them securely inside the block, then removes them after exiting the block.

Execution Sample

Jenkins

withCredentials([usernamePassword(credentialsId: 'myCreds', usernameVariable: 'USER', passwordVariable: 'PASS')]) {
  sh 'echo Using $USER and $PASS'
}
sh 'echo Credentials no longer available'

This Jenkins pipeline snippet uses withCredentials to inject username and password as environment variables only inside the block.

Process Table

Step	Action	Environment Variables	Command Run	Output
1	Enter withCredentials block	USER=myUser, PASS=myPass	sh 'echo Using $USER and $PASS'	Using myUser and myPass
2	Exit withCredentials block	USER and PASS removed	sh 'echo Credentials no longer available'	Credentials no longer available

💡 Credentials environment variables removed after withCredentials block ends to keep them secure

Status Tracker

Variable	Start	Inside withCredentials	After withCredentials
USER	undefined	myUser	undefined
PASS	undefined	myPass	undefined

Key Moments - 2 Insights

Why can't I access USER and PASS variables outside the withCredentials block?

Because the execution_table shows that USER and PASS are only set inside the withCredentials block and removed immediately after it ends to keep credentials secure.

What happens if I try to print the password outside the block?

The variable PASS is undefined outside the block, so the output will not show the password, as confirmed in the execution_table step 2.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of USER inside the withCredentials block?

A myPass

B myUser

C undefined

D CredentialsId

💡 Hint

Check the Environment Variables column at Step 1 in the execution_table

At which step are the credentials removed from environment variables?

A Step 2

B Step 1

C Before Step 1

D Credentials never removed

💡 Hint

Look at the Environment Variables column at Step 2 in the execution_table

If you try to use $PASS outside the withCredentials block, what happens?

A It prints the password

B It prints the username

C It prints nothing or error

D It prints the credentialsId

💡 Hint

Refer to variable_tracker showing PASS is undefined after withCredentials block

Concept Snapshot

withCredentials block securely injects credentials as environment variables
Credentials are only available inside the block
After block ends, credentials are removed from environment
Use credentials inside the block for secure access
Outside the block, variables are undefined
Prevents accidental credential leaks

Full Transcript

The withCredentials block in Jenkins pipelines is used to securely inject credentials as environment variables only inside the block. When the pipeline enters the block, the specified credentials are set as environment variables like USER and PASS. Commands inside the block can use these variables safely. Once the block finishes, the credentials are removed from the environment to prevent leaks. This means outside the block, the variables are undefined and cannot be accessed. This flow ensures credentials are only exposed for the minimum time needed during pipeline execution.