Parameterized builds in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a string parameter named 'ENV' in a Jenkins pipeline.

Jenkins

parameters {
    string(name: '[1]', defaultValue: 'dev', description: 'Environment')
}

Drag options to blanks, or click blank then click option'

AENV

Benvironment

CenvVar

Denv

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase or different names like 'env' or 'environment' which won't match the parameter usage.

The parameter name must exactly match 'ENV' to be used consistently in the pipeline.

2fill in blank

medium

Complete the code to access the parameter 'ENV' inside the Jenkins pipeline script.

Jenkins

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                echo "Building for environment: [1]"
            }
        }
    }
}

Drag options to blanks, or click blank then click option'

Abuild.ENV

Bparams.ENV

Cparameters.ENV

Denv.ENV

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'env.ENV' which refers to environment variables, not parameters.

Using 'parameters.ENV' which is not valid syntax.

In Jenkins pipelines, parameters are accessed using the 'params' object, e.g., params.ENV.

3fill in blank

hard

Fix the error in the parameter definition to correctly define a boolean parameter named 'RUN_TESTS'.

Jenkins

parameters {
    booleanParam(name: '[1]', defaultValue: true, description: 'Run tests')
}

Drag options to blanks, or click blank then click option'

ARUN_TESTS

BRunTests

Crun_tests

DrunTests

Attempts:

3 left

💡 Hint

Common Mistakes

Using camelCase or lowercase names that don't match the parameter usage.

Parameter names are case-sensitive and usually uppercase with underscores for clarity and consistency.

4fill in blank

hard

Fill both blanks to define a choice parameter named 'DEPLOY_ENV' with options 'dev', 'staging', and 'prod'.

Jenkins

parameters {
    choice(name: '[1]', choices: [2], description: 'Select deployment environment')
}

Drag options to blanks, or click blank then click option'

ADEPLOY_ENV

B['dev', 'staging', 'prod']

C['prod', 'staging', 'dev']

DDEPLOYENV

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect parameter names or wrong order of choices.

Not using a list format for choices.

The parameter name should be 'DEPLOY_ENV' and choices must be a list of strings in the desired order.

5fill in blank

hard

Fill all three blanks to create a pipeline that uses a string parameter 'VERSION', checks if it is not empty, and echoes the version.

Jenkins

pipeline {
    agent any
    parameters {
        string(name: '[1]', defaultValue: '', description: 'Version to build')
    }
    stages {
        stage('Check Version') {
            steps {
                script {
                    if (params.[2] [3] '') {
                        echo "Building version: ${params.VERSION}"
                    } else {
                        error 'Version parameter is empty!'
                    }
                }
            }
        }
    }
}

Drag options to blanks, or click blank then click option'

AVERSION

C!=

D==

Attempts:

3 left

💡 Hint

Common Mistakes

Using '==' instead of '!=' causing the logic to invert.

Mismatching parameter names between definition and usage.

The parameter name is 'VERSION'. To check if it is not empty, use 'params.VERSION != '''.

Practice

1.

What is the main purpose of parameterized builds in Jenkins?

easy

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

B. To automatically deploy builds to production

C. To schedule builds at specific times

D. To monitor server health during builds

Solution

1. Step 1: Understand parameterized builds concept

   Parameterized builds let users provide inputs that change how the build runs.

2. Step 2: Identify the main purpose

   The main goal is to customize the build without changing the job code.

3. Final Answer:

   To allow users to input values that customize the build process -> Option A

4. Quick Check:

   Parameterized builds = user inputs [OK]

Hint: Think: 'How do I change build behavior without editing code?' [OK]

Common Mistakes:

• Confusing parameterized builds with scheduling
• Thinking parameters deploy builds automatically
• Mixing monitoring with build customization

2.

Which of the following is the correct syntax to define a string parameter named ENV in a Jenkins pipeline?

parameters {
    ?
}

easy

A. paramString('ENV', 'dev', 'Environment')

B. string(name: 'ENV', defaultValue: 'dev', description: 'Environment')

C. stringParam('ENV', 'dev', 'Environment')

D. parameterString(name='ENV', default='dev')

Solution

1. Step 1: Recall Jenkins pipeline parameter syntax

   Jenkins uses string(name: '', defaultValue: '', description: '') inside parameters block.

2. Step 2: Match correct syntax

   string(name: 'ENV', defaultValue: 'dev', description: 'Environment') matches the correct syntax exactly.

3. Final Answer:

   string(name: 'ENV', defaultValue: 'dev', description: 'Environment') -> Option B

4. Quick Check:

   Correct parameter syntax = string(name: 'ENV', defaultValue: 'dev', description: 'Environment') [OK]

Hint: Remember: 'string' with named args inside parameters block [OK]

Common Mistakes:

• Using incorrect function names like stringParam
• Missing named arguments or using wrong argument names
• Confusing parameter syntax with freestyle job parameters

3.

Given this Jenkins pipeline snippet, what will be printed if the build is started with parameter BRANCH=feature?

pipeline {
  agent any
  parameters {
    string(name: 'BRANCH', defaultValue: 'main', description: 'Git branch')
  }
  stages {
    stage('Print Branch') {
      steps {
        echo "Building branch: ${params.BRANCH}"
      }
    }
  }
}

medium

A. Building branch: main

B. Error: BRANCH parameter not found

C. Building branch: feature

D. Building branch: ${params.BRANCH}

Solution

1. Step 1: Understand parameter usage in pipeline

   The parameter BRANCH has default 'main' but can be overridden at build start.

2. Step 2: Check what happens when build starts with BRANCH=feature

   The value 'feature' replaces default, so params.BRANCH is 'feature'.

3. Final Answer:

   Building branch: feature -> Option C

4. Quick Check:

   Parameter override prints new value [OK]

Hint: Parameter value at build start overrides default [OK]

Common Mistakes:

• Assuming default value always prints
• Thinking variable is not replaced in echo
• Confusing parameter name with environment variables

4.

Identify the error in this Jenkins pipeline snippet that defines a boolean parameter:

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

medium

A. The 'script' block is not allowed inside 'steps'

B. The parameter name should be 'boolean' not 'booleanParam'

C. The if condition should use 'params.deploy' in lowercase

D. The default value key should be 'defaultValue' not 'default'

Solution

1. Step 1: Check boolean parameter syntax

   Jenkins expects booleanParam(name: '', defaultValue: true/false, description: '').

2. Step 2: Identify incorrect key

   The snippet uses default instead of defaultValue, causing syntax error.

3. Final Answer:

   The default value key should be 'defaultValue' not 'default' -> Option D

4. Quick Check:

   Boolean param uses defaultValue key [OK]

Hint: Use 'defaultValue' for parameters, not 'default' [OK]

Common Mistakes:

• Using 'default' instead of 'defaultValue'
• Wrong parameter type name
• Incorrect case in parameter usage

5.

You want to create a Jenkins pipeline that asks for two parameters: a choice of ENV with options dev, qa, prod, and a boolean RUN_TESTS. The pipeline should print the selected environment and whether tests will run. Which snippet correctly defines these parameters and uses them in the Print Info stage?

hard

A. parameters {
choice(name: 'ENV', choices: ['dev', 'qa', 'prod'], description: 'Select environment')
booleanParam(name: 'RUN_TESTS', defaultValue: false, description: 'Run tests?')
}
stages {
stage('Print Info') {
steps {
echo "Environment: ${params.ENV}"
echo "Run tests: ${params.RUN_TESTS}"
}
}
}

B. parameters {
choice(name: 'ENV', choices: 'dev,qa,prod', description: 'Select environment')
boolean(name: 'RUN_TESTS', defaultValue: false, description: 'Run tests?')
}
stages {
stage('Print Info') {
steps {
echo "Environment: ${ENV}"
echo "Run tests: ${RUN_TESTS}"
}
}
}

C. parameters {
choice(name: 'ENV', choices: ['dev', 'qa', 'prod'], description: 'Select environment')
booleanParam(name: 'RUN_TESTS', default: false, description: 'Run tests?')
}
stages {
stage('Print Info') {
steps {
echo "Environment: ${params.ENV}"
echo "Run tests: ${params.RUN_TESTS}"
}
}
}

D. parameters {
choice(name: 'ENV', choices: 'dev,qa,prod', description: 'Select environment')
booleanParam(name: 'RUN_TESTS', defaultValue: false, description: 'Run tests?')
}
stages {
stage('Print Info') {
steps {
echo "Environment: ${params.ENV}"
echo "Run tests: ${params.RUN_TESTS}"
}
}
}

Solution

1. Step 1: Verify parameter definitions

   Choice parameter requires choices as a list, boolean parameter uses booleanParam with defaultValue.

2. Step 2: Check parameter usage in steps

   Parameters must be accessed as params.ENV and params.RUN_TESTS inside echo.

3. Final Answer:

   parameters { choice(name: 'ENV', choices: ['dev', 'qa', 'prod'], description: 'Select environment') booleanParam(name: 'RUN_TESTS', defaultValue: false, description: 'Run tests?') } stages { stage('Print Info') { steps { echo "Environment: ${params.ENV}" echo "Run tests: ${params.RUN_TESTS}" } } } -> Option A

4. Quick Check:

   Correct parameter syntax + params usage = parameters { choice(name: 'ENV', choices: ['dev', 'qa', 'prod'], description: 'Select environment') booleanParam(name: 'RUN_TESTS', defaultValue: false, description: 'Run tests?') } stages { stage('Print Info') { steps { echo "Environment: ${params.ENV}" echo "Run tests: ${params.RUN_TESTS}" } } } [OK]

Hint: Use list for choices and 'params.' prefix to access parameters [OK]

Common Mistakes:

• Passing choices as comma string instead of list
• Using 'default' instead of 'defaultValue' for booleanParam
• Accessing parameters without 'params.' prefix