Dynamic parameter values in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Dynamic Parameter Values in Jenkins

In Jenkins, dynamic parameters allow parameter values to be generated at build time. Which of the following best describes how dynamic parameter values are typically generated?

A By manually entering parameter values each time the build runs

B By hardcoding all parameter values in the Jenkinsfile before the build starts

C By using a Groovy script or external script to generate parameter values when the build is triggered

D By setting static environment variables in the Jenkins global configuration

💡 Hint

Think about how Jenkins can run scripts to fetch or calculate values just before the build starts.

Dynamic parameters in Jenkins are generated at build time using scripts, often Groovy scripts, which can query external systems or compute values dynamically. This allows parameter options to reflect the current state or environment.

💻 Command Output

intermediate

Output of a Groovy Script for Dynamic Parameters

Given the following Groovy script used in a Jenkins Active Choices parameter to generate a list of branches from a Git repository, what is the expected output?

Jenkins

def branches = ['main', 'develop', 'feature-x']
return branches

A ['main', 'develop', 'feature-x']

B main, develop, feature-x

C Error: Missing return statement

D null

💡 Hint

The script returns a list object directly.

The script defines a list of branch names and returns it. Jenkins expects the script to return a list or array for dynamic parameters.

❓ Configuration

advanced

Configuring a Dynamic Choice Parameter in Jenkinsfile

Which Jenkinsfile snippet correctly defines a dynamic choice parameter that lists files in the workspace directory at build time?

A properties([parameters([choice(name: 'FILES', choices: sh(script: 'ls', returnStdout: true), description: 'Select a file')])])

B properties([parameters([activeChoiceParam(name: 'FILES') { script { return ['file1', 'file2'] } }])])

C properties([parameters([choice(name: 'FILES', choices: ['file1', 'file2'], description: 'Select a file')])])

D properties([parameters([activeChoiceParam(name: 'FILES') { script { return sh(script: 'ls', returnStdout: true).split('\n') } }])])

💡 Hint

Look for the option that uses a script to dynamically list files at build time.

Option D uses an activeChoiceParam with a Groovy script that runs a shell command to list files and splits the output into a list, which is the correct way to create dynamic choices in Jenkinsfile.

❓ Troubleshoot

advanced

Troubleshooting Dynamic Parameter Script Failure

A Jenkins Active Choices parameter script that queries an external API to generate options suddenly fails with a timeout error. What is the most likely cause?

A The script syntax is invalid and causes a compilation error

B The Jenkins agent does not have network access to the external API

C The parameter name is missing in the Jenkinsfile

D The Jenkins master is offline

💡 Hint

Consider connectivity issues when scripts call external services.

If the script calls an external API and times out, it usually means the Jenkins agent running the script cannot reach the API due to network restrictions or firewall rules.

🔀 Workflow

expert

Implementing a Multi-Level Dynamic Parameter Workflow

You want to create a Jenkins job with two dynamic parameters: the first lists available projects, and the second lists branches for the selected project. Which workflow correctly implements this multi-level dynamic parameter setup?

A Use two Active Choices parameters where the second parameter's script reads the first parameter's value and queries branches accordingly

B Use two static choice parameters with hardcoded project and branch lists

C Use a single parameter that combines project and branch names in one list

D Use environment variables to pass project and branch names between builds

💡 Hint

Think about how one parameter can depend on another's value dynamically.

Option A correctly uses two Active Choices parameters where the second parameter's script dynamically reads the first parameter's selected value to generate relevant branch options, enabling multi-level dynamic selection.