Parameterized builds in Jenkins - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a parameterized build in Jenkins?

A parameterized build lets you run a Jenkins job with input values (parameters) that you provide when starting the build. This makes the build flexible and reusable for different situations.

beginner

Name two common types of parameters used in Jenkins parameterized builds.

Two common parameter types are String Parameter (text input) and Boolean Parameter (true/false checkbox).

beginner

How do you add parameters to a Jenkins job?

In the job configuration, check 'This project is parameterized' and then add the desired parameter types with names and default values.

intermediate

How can you use parameters inside a Jenkins Pipeline script?

You access parameters using the 'params' object, for example: params.MY_PARAM to get the value of a parameter named MY_PARAM.

beginner

Why are parameterized builds useful in real-life projects?

They let you customize builds without changing the job itself. For example, you can build different versions, deploy to different environments, or run tests with different settings.

What must you enable in a Jenkins job to accept input parameters?

A Set 'Discard old builds'

B Enable 'Build periodically'

C Check 'This project is parameterized'

D Add a post-build action

To use parameters, you must check 'This project is parameterized' in the job configuration.

Which Jenkins parameter type lets you choose true or false?

A Boolean Parameter

B Choice Parameter

C String Parameter

D File Parameter

Boolean Parameter provides a checkbox for true or false input.

How do you access a parameter named 'VERSION' in a Jenkins Pipeline script?

A input.VERSION

B env.VERSION

C build.VERSION

D params.VERSION

In Pipeline scripts, parameters are accessed via the 'params' object.

What happens if you run a parameterized build without providing a parameter value?

A The default parameter value is used

B The build fails immediately

C Jenkins asks for the value during the build

D The build ignores parameters

If no value is provided, Jenkins uses the default value set for the parameter.

Which of these is NOT a benefit of parameterized builds?

A Reusing the same job for different inputs

B Automatically fixing build errors

C Customizing builds without changing job config

D Deploying to different environments easily

Parameterized builds do not fix errors automatically; they only allow input customization.

Explain how to configure a Jenkins job to accept parameters and how to use those parameters in a Pipeline script.

Think about the job settings and how scripts read inputs.

Describe a real-world scenario where parameterized builds improve the build process.

Consider flexibility and reuse in builds.