Idempotent pipeline steps in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why are idempotent steps important in Jenkins pipelines?

Imagine you run a Jenkins pipeline multiple times. Why should the steps be idempotent?

A To make the pipeline run faster by skipping all steps after the first run.

B To ensure the pipeline produces the same result without causing errors or side effects when rerun.

C To allow the pipeline to use different tools each time it runs.

D To guarantee the pipeline only runs once and never again.

💡 Hint

Think about what happens if a step changes something every time it runs.

Idempotent steps mean running them multiple times won't change the outcome or cause errors. This is important for reliability and repeatability.

💻 Command Output

intermediate

Output of an idempotent shell step in Jenkins

What will be the output of this Jenkins pipeline shell step if run twice?

sh 'mkdir -p /tmp/myfolder && echo Created'

A

Created
Created

B

Created
mkdir: cannot create directory '/tmp/myfolder': File exists

C

Created
(no output second time)

D Error: Directory already exists

💡 Hint

Check what the -p option does for mkdir.

The -p option makes mkdir create the directory only if it doesn't exist, so no error occurs on the second run.

❓ Configuration

advanced

Ensuring idempotency in Jenkins pipeline environment setup

Which Jenkins pipeline snippet ensures the environment variable MY_VAR is set only if not already defined, making the step idempotent?

A environment { MY_VAR = "default"; MY_VAR = "override" }

B environment { MY_VAR = "default" }

C environment { MY_VAR = env.MY_VAR ?: "default" }

D environment { MY_VAR = env.MY_VAR && "default" }

💡 Hint

Use Groovy's Elvis operator to check if MY_VAR is already set.

Option C uses env.MY_VAR ?: "default" which sets MY_VAR only if it is not already defined, making it idempotent.

❓ Troubleshoot

advanced

Troubleshooting non-idempotent Jenkins pipeline step

A Jenkins pipeline step runs a script that appends a line to a file every time it runs. What problem does this cause?

A The file is deleted after each run, losing data.

B The script fails with a syntax error on the second run.

C The pipeline skips this step automatically after the first run.

D The file grows with duplicate lines, causing unexpected behavior or errors.

💡 Hint

Think about what happens if you add the same line repeatedly.

Appending without checking causes the file to grow with repeated lines, which can break logic depending on that file.

🔀 Workflow

expert

Idempotent deployment step in Jenkins pipeline

Which Jenkins pipeline step best ensures an idempotent deployment of a Docker container named myapp?

A sh 'docker rm -f myapp || true && docker run -d --name myapp myimage'

B sh 'docker run -d --name myapp myimage'

C sh 'docker start myapp || docker run -d --name myapp myimage'

D sh 'docker stop myapp && docker run -d --name myapp myimage'

💡 Hint

Consider how to remove any existing container before running a new one without failing.

Option A force removes any existing container named myapp (ignoring errors) before running a new one, ensuring idempotency.