Environment variables access in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Accessing environment variables in a Jenkins pipeline

What will be the output of the following Jenkins pipeline script snippet?

Jenkins

pipeline {
  agent any
  environment {
    MY_VAR = 'hello'
  }
  stages {
    stage('Print') {
      steps {
        script {
          echo "Value is: ${env.MY_VAR}"
        }
      }
    }
  }
}

A Value is: hello

B Value is: ${MY_VAR}

C Value is:

D Error: MY_VAR not defined

💡 Hint

Remember how environment variables are accessed in Jenkins pipeline scripts using env.

In Jenkins scripted or declarative pipelines, environment variables defined in the environment block are accessed using env.VARIABLE_NAME. Here, env.MY_VAR returns 'hello'.

🧠 Conceptual

intermediate

Understanding environment variable scope in Jenkins

Which statement correctly describes the scope of environment variables defined inside a Jenkins pipeline's environment block?

A They are available only after the pipeline finishes.

B They are available throughout the entire pipeline run.

C They are available only to the shell commands but not to Groovy scripts.

D They are available only within the stage where they are defined.

💡 Hint

Think about when environment variables are set and how Jenkins shares them.

Environment variables defined in the environment block are set for the entire pipeline run and are accessible in all stages and steps.

❓ Troubleshoot

advanced

Troubleshooting missing environment variable in Jenkins shell step

A Jenkins pipeline defines an environment variable MY_SECRET in the environment block. However, when running a shell step, the variable is empty. What is the most likely cause?

A Jenkins does not support environment variables in shell steps.

B The environment variable was not defined in the environment block.

C The shell step uses single quotes around the variable reference, preventing expansion.

D The variable name is case-insensitive and was misspelled.

💡 Hint

Check how shell interprets quotes and variable expansion.

In shell scripts, variables inside single quotes are not expanded. Using double quotes or no quotes allows expansion of environment variables.

🔀 Workflow

advanced

Passing environment variables between Jenkins pipeline stages

Which method correctly passes an environment variable set in one stage to another stage in a Jenkins declarative pipeline?

A Set the variable in the environment block at the pipeline level.

B Use the 'withEnv' step inside each stage separately.

C Set the variable inside a stage's script block and access it directly in the next stage.

D Use 'sh export VAR=value' in one stage and access VAR in the next stage shell step.

💡 Hint

Think about where environment variables must be declared to persist across stages.

Environment variables declared in the pipeline-level environment block are available in all stages. Variables set inside a stage or shell command do not persist to other stages.

✅ Best Practice

expert

Secure handling of sensitive environment variables in Jenkins

What is the recommended best practice to securely use sensitive environment variables like passwords in Jenkins pipelines?

A Print sensitive variables in console logs for debugging.

B Store sensitive values directly in the pipeline script environment block.

C Hardcode secrets in shell commands inside the pipeline.

D Use Jenkins Credentials plugin and access secrets via credentials binding.

💡 Hint

Consider how Jenkins manages secrets securely.

The Jenkins Credentials plugin securely stores secrets and injects them into pipelines without exposing them in logs or code.