Environment variables in builds in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins environment variable usage in shell step

In a Jenkins pipeline, you have set an environment variable MY_VAR with value hello. What will be the output of the following shell step?

sh 'echo $MY_VAR'

Jenkins

pipeline {
  agent any
  environment {
    MY_VAR = 'hello'
  }
  stages {
    stage('Print') {
      steps {
        sh 'echo $MY_VAR'
      }
    }
  }
}

A SyntaxError

B $MY_VAR

C null

D hello

💡 Hint

Remember how shell variables are accessed inside shell steps in Jenkins.

In Jenkins shell steps, environment variables are accessed using the shell syntax with a dollar sign, so $MY_VAR expands to 'hello'.

🧠 Conceptual

intermediate

Scope of environment variables in Jenkins pipeline

Which statement about environment variables in Jenkins declarative pipelines is true?

A Environment variables set inside a <code>script</code> block are automatically global.

B Environment variables set in the <code>environment</code> block are available to all stages and steps.

C Environment variables cannot be accessed in <code>sh</code> steps.

D Environment variables must be declared in the Jenkins system configuration to be used in pipelines.

💡 Hint

Think about where you declare environment variables in a declarative pipeline.

The environment block in a declarative pipeline sets variables that are available throughout the pipeline's stages and steps.

❓ Troubleshoot

advanced

Why does a Jenkins shell step not see a custom environment variable?

You set an environment variable MY_VAR inside a script block using env.MY_VAR = 'test'. But when you run sh 'echo $MY_VAR' in the next step, it prints empty. Why?

A Because environment variables set in <code>script</code> blocks are not automatically exported to shell steps.

B Because <code>sh</code> steps cannot access any environment variables.

C Because <code>env.MY_VAR</code> must be declared in the <code>environment</code> block to be visible.

D Because shell steps require variables to be passed as parameters explicitly.

💡 Hint

Consider how Jenkins passes environment variables to shell steps.

Setting env.MY_VAR inside a script block changes the variable for the Groovy environment but does not export it to the shell environment automatically.

🔀 Workflow

advanced

Passing environment variables between Jenkins pipeline stages

You want to set an environment variable VERSION in one stage and use it in a later stage. Which approach works correctly?

A Set <code>env.VERSION = '1.0'</code> in the first stage inside a <code>script</code> block; it will be available in later stages.

B Use the <code>environment</code> block at the pipeline level and update <code>VERSION</code> dynamically in the first stage.

C Write the variable to a file in the first stage and read it in the next stage.

D Set <code>VERSION</code> as a global variable in Jenkins system configuration.

💡 Hint

Think about how Jenkins pipeline stages run in separate processes.

Each stage runs in a separate process, so environment variables set in one stage do not persist automatically. Writing to a file and reading it later is a common way to share data.

✅ Best Practice

expert

Secure handling of sensitive environment variables in Jenkins builds

Which is the best practice to handle sensitive environment variables like passwords in Jenkins pipelines?

A Store sensitive variables in Jenkins Credentials and inject them using the <code>credentials()</code> helper.

B Hardcode sensitive variables directly in the <code>environment</code> block for easy access.

C Print sensitive variables in console logs for debugging purposes.

D Store sensitive variables in plain text files inside the workspace.

💡 Hint

Think about security and Jenkins features for secrets.

Jenkins Credentials plugin securely stores secrets and allows injecting them without exposing in logs or code.