Avoiding hard-coded values in Jenkins - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does 'avoiding hard-coded values' mean in Jenkins pipelines?

It means not writing fixed values directly in the pipeline script. Instead, use variables or parameters so you can change values without editing the code.

beginner

Why should you avoid hard-coded values in Jenkins pipelines?

Because hard-coded values make scripts less flexible and harder to maintain. Using variables or parameters helps reuse the pipeline for different projects or environments easily.

intermediate

How can you pass values to a Jenkins pipeline without hard-coding?

You can use parameters in the pipeline, environment variables, or external configuration files to pass values dynamically.

beginner

Example: How to define a string parameter in a Jenkins declarative pipeline?

Use the parameters block like this:<br>

parameters {
  string(name: 'BRANCH_NAME', defaultValue: 'main', description: 'Git branch to build')
}

intermediate

What is the benefit of using environment variables in Jenkins pipelines?

Environment variables let you store values outside the code and reuse them in multiple places. This avoids repeating hard-coded values and makes updates easier.

Which method helps avoid hard-coded values in Jenkins pipelines?

A Using parameters and environment variables

B Writing fixed values directly in the script

C Copy-pasting the same value multiple times

D Ignoring configuration files

Using parameters and environment variables allows dynamic input and avoids fixed values in the pipeline.

How do you define a string parameter in a Jenkins declarative pipeline?

A env { PARAM = 'value' }

B parameters { string(name: 'PARAM', defaultValue: 'value', description: 'desc') }

C stage('Param') { steps { echo 'value' } }

D node { param('PARAM') }

The parameters block with string() defines a string parameter for the pipeline.

What is a risk of hard-coding values in Jenkins pipelines?

A Parameters are automatically created

B Pipelines run faster

C Scripts become less flexible and harder to update

D Environment variables are ignored

Hard-coded values reduce flexibility and make maintenance difficult.

Which of these is NOT a way to avoid hard-coded values?

A Writing fixed values directly in the script

B Using pipeline parameters

C Using environment variables

D Using external configuration files

Writing fixed values directly is exactly what we want to avoid.

What does the 'environment' block in Jenkins pipeline do?

A Runs shell commands

B Sets pipeline parameters

C Declares pipeline stages

D Defines environment variables for the pipeline

The environment block sets environment variables accessible during the pipeline run.

Explain why avoiding hard-coded values is important in Jenkins pipelines and how you can implement it.

Think about how changing values without editing code helps.

Describe how to define and use a string parameter in a Jenkins declarative pipeline.

Look for the parameters { string(...) } syntax.