Environment directive in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this Jenkins pipeline environment variable?

Consider this Jenkins pipeline snippet:

pipeline {
  agent any
  environment {
    GREETING = 'Hello'
    TARGET = 'World'
  }
  stages {
    stage('Print') {
      steps {
        script {
          echo "${GREETING}, ${TARGET}!"
        }
      }
    }
  }
}

What will be printed in the console output?

Jenkins

pipeline {
  agent any
  environment {
    GREETING = 'Hello'
    TARGET = 'World'
  }
  stages {
    stage('Print') {
      steps {
        script {
          echo "${GREETING}, ${TARGET}!"
        }
      }
    }
  }
}

A Hello, ${TARGET}!

B ${GREETING}, ${TARGET}!

C Hello, World!

D GREETING, TARGET!

💡 Hint

Remember that environment variables defined in the environment block are accessible inside steps using ${VARIABLE_NAME}.

The environment directive sets variables that are accessible in the pipeline steps. Using ${GREETING} and ${TARGET} inside echo will substitute their values.

❓ Configuration

intermediate

Which environment directive syntax correctly sets a variable with a shell command output?

You want to set an environment variable CURRENT_DATE to the output of the shell command date in a Jenkins pipeline environment block. Which option correctly does this?

A

environment {
  CURRENT_DATE = "${sh 'date'}"
}

B

environment {
  CURRENT_DATE = sh(script: 'date', returnStdout: true).trim()
}

C

environment {
  CURRENT_DATE = "$(date)"
}

D

environment {
  CURRENT_DATE = sh('date')
}

💡 Hint

In Jenkins declarative pipeline, environment variables cannot directly run shell commands. You must use a script block or special syntax.

Only option B uses the correct syntax to run a shell command and assign its trimmed output to an environment variable in a declarative pipeline.

❓ Troubleshoot

advanced

Why does this environment variable not get set as expected?

Given this Jenkins pipeline snippet:

pipeline {
  agent any
  environment {
    PATH = '/custom/path'
  }
  stages {
    stage('Check') {
      steps {
        sh 'echo $PATH'
      }
    }
  }
}

The output shows only the default PATH, not '/custom/path'. Why?

Jenkins

pipeline {
  agent any
  environment {
    PATH = '/custom/path'
  }
  stages {
    stage('Check') {
      steps {
        sh 'echo $PATH'
      }
    }
  }
}

A The environment directive overrides PATH, but the shell step resets PATH to default for security.

B The shell step runs in a separate shell that does not inherit Jenkins environment variables.

C The PATH variable is overridden but the shell uses a cached PATH ignoring Jenkins variables.

D The environment directive overrides PATH only inside the Jenkins process, not the shell environment.

💡 Hint

Some environment variables like PATH are treated specially by Jenkins for security reasons.

Jenkins resets PATH in shell steps to avoid security risks. Overriding PATH in environment does not affect shell steps unless explicitly handled.

🔀 Workflow

advanced

How to pass environment variables between stages in a declarative pipeline?

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

A Use the stash/unstash steps to pass environment variables between stages.

B Set the variable in one stage's environment block and it will automatically be available in later stages.

C Use script block to set a global variable and then assign it to environment in later stages.

D Set the variable in the environment block at pipeline level so all stages can access it.

💡 Hint

Environment variables defined at the pipeline level are global to all stages.

Only environment variables defined at the pipeline level environment block are available in all stages. Stage-level environment blocks are local to that stage.

✅ Best Practice

expert

What is the best practice for securely handling sensitive environment variables in Jenkins pipelines?

You need to use a secret API key in your Jenkins pipeline environment. Which method is the best practice to handle this securely?

A Store the API key in Jenkins credentials and use the credentials binding plugin to inject it as an environment variable.

B Hardcode the API key in the environment block of the Jenkinsfile for easy access.

C Store the API key in a plain text file in the repository and read it during the pipeline.

D Pass the API key as a parameter to the pipeline and print it in the logs for debugging.

💡 Hint

Avoid exposing secrets in code or logs. Use Jenkins built-in secure storage.

Using Jenkins credentials and credentials binding plugin securely injects secrets as environment variables without exposing them in code or logs.