Parameterized builds in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Parameterized Builds in Jenkins

What is the main purpose of using parameterized builds in Jenkins?

A To allow users to input values that customize the build process at runtime

B To create multiple Jenkins jobs with the same configuration

C To schedule builds to run at fixed times without parameters

D To automatically deploy builds without any user input

💡 Hint

Think about how you can make a build flexible by asking for input before it starts.

Parameterized builds let users provide input values when starting a build, so the build can behave differently based on those inputs.

💻 Command Output

intermediate

Output of a Parameterized Build with String Parameter

Given a Jenkins pipeline with a string parameter ENV defaulting to dev, what will be the output of the following snippet if the build is triggered with ENV=prod?

pipeline {
  agent any
  parameters {
    string(name: 'ENV', defaultValue: 'dev', description: 'Environment')
  }
  stages {
    stage('Print Env') {
      steps {
        echo "Deploying to ${params.ENV} environment"
      }
    }
  }
}

A Error: params.ENV is undefined

B Deploying to dev environment

C Deploying to ${params.ENV} environment

D Deploying to prod environment

💡 Hint

Remember that parameters override default values when provided at build time.

The parameter ENV is set to prod at build time, so the echo prints that value.

❓ Configuration

advanced

Configuring a Boolean Parameter in Jenkins Pipeline

Which of the following Jenkins pipeline snippets correctly defines a boolean parameter named RUN_TESTS with a default value of true?

A parameters { boolean(name: 'RUN_TESTS', defaultValue: true, description: 'Run tests?') }

B parameters { booleanParam(name: 'RUN_TESTS', defaultValue: true, description: 'Run tests?') }

C parameters { boolParam(name: 'RUN_TESTS', defaultValue: true, description: 'Run tests?') }

D parameters { booleanParameter(name: 'RUN_TESTS', defaultValue: true, description: 'Run tests?') }

💡 Hint

Check the exact syntax for boolean parameters in Jenkins declarative pipeline.

The correct syntax uses booleanParam to define a boolean parameter in Jenkins pipeline.

❓ Troubleshoot

advanced

Troubleshooting Missing Parameter Value in Jenkins Build

A Jenkins job is configured with a string parameter VERSION. When triggered manually, the build fails with the error groovy.lang.MissingPropertyException: No such property: VERSION. What is the most likely cause?

A The parameter <code>VERSION</code> was not defined in the pipeline parameters block

B The parameter <code>VERSION</code> was defined but misspelled in the script as <code>version</code>

C The build was triggered without selecting the parameter option

D The Jenkins server is down

💡 Hint

Think about how Jenkins exposes parameters to the pipeline script.

If the parameter is not declared in the pipeline, Jenkins does not create the variable, causing the error.

🔀 Workflow

expert

Best Workflow to Use Parameters for Conditional Deployment

You want to create a Jenkins pipeline that deploys to different environments based on a parameter DEPLOY_ENV which can be dev, staging, or prod. Which pipeline snippet correctly implements this conditional deployment?

pipeline {
  agent any
  parameters {
    choice(name: 'DEPLOY_ENV', choices: ['dev', 'staging', 'prod'], description: 'Select environment')
  }
  stages {
    stage('Deploy') {
      steps {
        script {
          // Fill in conditional deployment here
        }
      }
    }
  }
}

A when { environment name: 'DEPLOY_ENV', value: 'dev' } { echo 'Deploying to dev' }

B match(params.DEPLOY_ENV) { case 'dev' -> echo 'Deploying to dev'; case 'staging' -> echo 'Deploying to staging'; case 'prod' -> echo 'Deploying to prod'; }

C if (params.DEPLOY_ENV == 'dev') { echo 'Deploying to dev' } else if (params.DEPLOY_ENV == 'staging') { echo 'Deploying to staging' } else { echo 'Deploying to prod' }

D switch(params.DEPLOY_ENV) { case 'dev': echo 'Deploying to dev'; break; case 'staging': echo 'Deploying to staging'; break; case 'prod': echo 'Deploying to prod'; break; }

💡 Hint

Use Groovy script inside the script block to handle conditions.

Option C uses standard Groovy if-else statements inside the script block, which is the correct way to handle parameter-based conditions in Jenkins pipeline.