Environment variables access in Jenkins - Step-by-Step Execution

Process Flow - Environment variables access

Start Jenkins Job

↓

Load Environment Variables

↓

Access Variables in Pipeline

↓

Use Variables in Steps

↓

Job Execution Continues

↓

Job Ends

This flow shows how Jenkins loads environment variables at job start, then the pipeline accesses and uses them during execution.

Execution Sample

Jenkins

pipeline {
  agent any
  stages {
    stage('Print Env') {
      steps {
        echo "PATH is ${env.PATH}"
      }
    }
  }
}

This Jenkins pipeline prints the PATH environment variable during the 'Print Env' stage.

Process Table

Step	Action	Environment Variable Accessed	Value Retrieved	Output
1	Start Jenkins Job	N/A	N/A	Job starts, environment variables loaded
2	Enter 'Print Env' stage	PATH	/usr/bin:/bin:/usr/sbin:/sbin	Ready to use PATH variable
3	Execute echo step	PATH	/usr/bin:/bin:/usr/sbin:/sbin	Prints: PATH is /usr/bin:/bin:/usr/sbin:/sbin
4	Stage completes	N/A	N/A	Stage finished successfully
5	Job ends	N/A	N/A	Job execution complete

💡 Job ends after all stages complete

Status Tracker

Variable	Start	After Step 2	After Step 3	Final
env.PATH	N/A	/usr/bin:/bin:/usr/sbin:/sbin	/usr/bin:/bin:/usr/sbin:/sbin	/usr/bin:/bin:/usr/sbin:/sbin

Key Moments - 2 Insights

Why do we use env.PATH instead of just PATH in the pipeline?

In Jenkins pipelines, environment variables are accessed via the env object (like env.PATH). This is shown in execution_table step 3 where echo uses ${env.PATH} to get the value.

What happens if we try to access an environment variable that does not exist?

If the variable does not exist, env.VAR returns null or empty string. The pipeline will print nothing or empty value. This is implied by the variable_tracker showing only existing variables.

Visual Quiz - 3 Questions

Look at the execution table, what is printed at step 3?

A PATH is null

B PATH is empty

C PATH is /usr/bin:/bin:/usr/sbin:/sbin

D Error accessing PATH

💡 Hint

Check the Output column at step 3 in the execution_table

At which step does the pipeline actually access the environment variable PATH?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the Environment Variable Accessed column in execution_table

If we tried to print a variable not set in the environment, what would happen?

A Pipeline prints an empty string or nothing

B Pipeline prints the variable name

C Pipeline crashes immediately

D Pipeline prints 'undefined'

💡 Hint

Refer to key_moments explanation about missing variables

Concept Snapshot

Jenkins pipelines access environment variables via the env object.
Use syntax ${env.VAR_NAME} inside steps.
Variables are loaded at job start.
If variable missing, value is empty or null.
Use echo to print variables for debugging.

Full Transcript

This visual execution shows how Jenkins pipelines access environment variables. When a Jenkins job starts, it loads environment variables from the system. Inside the pipeline, these variables are accessed using the env object, for example env.PATH. The example pipeline prints the PATH variable during the 'Print Env' stage. The execution table traces each step: job start, entering the stage, accessing PATH, printing it, and job completion. The variable tracker shows env.PATH value remains constant during execution. Key moments clarify why env.PATH syntax is used and what happens if a variable is missing. The quiz tests understanding of when and how variables are accessed and printed. This helps beginners see environment variable usage in Jenkins pipelines step-by-step.