String, boolean, and choice parameters in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of Jenkinsfile with String Parameter

Given this Jenkinsfile snippet, what will be the output when the build is triggered with the default parameter value?

pipeline {
  agent any
  parameters {
    string(name: 'GREETING', defaultValue: 'Hello', description: 'Greeting message')
  }
  stages {
    stage('Print') {
      steps {
        echo params.GREETING
      }
    }
  }
}

Jenkins

pipeline {
  agent any
  parameters {
    string(name: 'GREETING', defaultValue: 'Hello', description: 'Greeting message')
  }
  stages {
    stage('Print') {
      steps {
        echo params.GREETING
      }
    }
  }
}

A Hello

B GREETING

C null

D Error: params.GREETING undefined

💡 Hint

Look at the defaultValue set in the string parameter.

The string parameter GREETING has a default value 'Hello'. If the build is triggered without changing it, params.GREETING will be 'Hello'.

💻 Command Output

intermediate

Boolean Parameter Effect on Build

Consider this Jenkinsfile snippet with a boolean parameter. What will be printed if the build is triggered with the boolean parameter unchecked?

pipeline {
  agent any
  parameters {
    booleanParam(name: 'DEPLOY', defaultValue: true, description: 'Deploy to production?')
  }
  stages {
    stage('Check') {
      steps {
        script {
          if (params.DEPLOY) {
            echo 'Deploying...'
          } else {
            echo 'Skipping deploy'
          }
        }
      }
    }
  }
}

Jenkins

pipeline {
  agent any
  parameters {
    booleanParam(name: 'DEPLOY', defaultValue: true, description: 'Deploy to production?')
  }
  stages {
    stage('Check') {
      steps {
        script {
          if (params.DEPLOY) {
            echo 'Deploying...'
          } else {
            echo 'Skipping deploy'
          }
        }
      }
    }
  }
}

A false

B Deploying...

C true

D Skipping deploy

💡 Hint

Boolean parameters are true if checked, false if unchecked.

If the boolean parameter DEPLOY is unchecked, params.DEPLOY is false, so the else branch runs printing 'Skipping deploy'.

💻 Command Output

advanced

Choice Parameter Value in Jenkins Pipeline

What will be the output of this Jenkins pipeline if the choice parameter 'ENV' is set to 'staging' when the build starts?

pipeline {
  agent any
  parameters {
    choice(name: 'ENV', choices: ['dev', 'staging', 'prod'], description: 'Select environment')
  }
  stages {
    stage('Show Env') {
      steps {
        echo "Selected environment is: ${params.ENV}"
      }
    }
  }
}

Jenkins

pipeline {
  agent any
  parameters {
    choice(name: 'ENV', choices: ['dev', 'staging', 'prod'], description: 'Select environment')
  }
  stages {
    stage('Show Env') {
      steps {
        echo "Selected environment is: ${params.ENV}"
      }
    }
  }
}

A Selected environment is: prod

B Selected environment is: staging

C Selected environment is: dev

D Selected environment is: ENV

💡 Hint

The output uses the value of params.ENV which is set by the choice parameter.

The choice parameter ENV is set to 'staging' at build start, so params.ENV equals 'staging'. The echo prints that value.

❓ Troubleshoot

advanced

Troubleshooting Undefined Parameter in Jenkinsfile

A Jenkins pipeline uses a boolean parameter named 'RUN_TESTS'. The pipeline fails with an error: groovy.lang.MissingPropertyException: No such property: RUN_TESTS. What is the most likely cause?

Options:

A The parameter was not defined in the parameters block of the Jenkinsfile.

B The parameter name is misspelled in the script as 'RUN_TESTS'.

C Boolean parameters cannot be accessed via params in Jenkins pipelines.

D The Jenkins agent does not support boolean parameters.

💡 Hint

Check if the parameter is declared properly in the Jenkinsfile.

If the parameter is not declared in the parameters block, params.RUN_TESTS is undefined, causing the MissingPropertyException.

✅ Best Practice

expert

Best Practice for Secure Use of String Parameters

Which practice is best to securely handle sensitive data passed as a string parameter in Jenkins pipelines?

A Use a string parameter and print its value in the console for debugging.

B Store sensitive data directly in the Jenkinsfile as plain text.

C Use a string parameter but mask its value in the console output using Jenkins credentials binding.

D Use a choice parameter with all possible sensitive values listed.

💡 Hint

Think about how to avoid exposing secrets in logs.

Masking sensitive string parameters using Jenkins credentials or masking plugins prevents secrets from appearing in logs, improving security.