Creating reusable pipeline steps in Jenkins - Practice Exercises

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the main benefit of using reusable pipeline steps in Jenkins?

Why should you create reusable pipeline steps in Jenkins pipelines?

A To increase the pipeline execution time by adding more steps

B To avoid repeating the same code and make pipelines easier to maintain

C To make the pipeline code more complex and harder to understand

D To prevent the pipeline from running on multiple agents

💡 Hint

Think about how repeating code affects maintenance.

Reusable steps help avoid code duplication, making pipelines simpler and easier to update.

💻 Command Output

intermediate

Output of calling a shared library step in Jenkins pipeline

Given this Jenkinsfile snippet calling a shared library step buildApp(), what will be the output?

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        script {
          buildApp()
        }
      }
    }
  }
}

// Assume buildApp() prints 'Building application...'

A No output, step is skipped

B Error: buildApp() is not defined

C Pipeline fails with syntax error

D Building application...

💡 Hint

Shared library steps are reusable functions defined outside the Jenkinsfile.

If the shared library is properly loaded, calling buildApp() runs its code and prints the message.

❓ Configuration

advanced

How to define a reusable step in a Jenkins shared library

Which of the following is the correct way to define a reusable step named deployApp in a Jenkins shared library?

A def deployApp() { echo 'Deploying application...' }

B step deployApp { echo 'Deploying application...' }

C function deployApp() { echo 'Deploying application...' }

D deployApp() => { echo 'Deploying application...' }

💡 Hint

Shared library steps are usually Groovy methods starting with def.

In Jenkins shared libraries, reusable steps are defined as Groovy methods using def.

🔀 Workflow

advanced

Order of execution in a Jenkins pipeline using reusable steps

Given these reusable steps called in order: checkoutCode(), buildApp(), testApp(), what is the correct order of execution in the pipeline?

A 2,1,3

B 3,2,1

C 1,2,3

D 1,3,2

💡 Hint

Think about the logical order: get code, build, then test.

The pipeline must first checkout code, then build it, and finally run tests.

❓ Troubleshoot

expert

Why does calling a reusable step cause 'No such DSL method' error?

You have defined a reusable step deployApp() in your shared library, but Jenkins pipeline fails with No such DSL method 'deployApp'. What is the most likely cause?

A The shared library is not properly loaded or configured in the pipeline

B The deployApp() method has a syntax error inside its definition

C The Jenkins agent does not have enough memory to run the step

D The pipeline script is missing the <code>agent any</code> declaration

💡 Hint

Check if the shared library is declared in the pipeline or global configuration.

This error usually means Jenkins cannot find the step because the shared library is not loaded or referenced correctly.