Loading libraries in Jenkinsfile - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of loading a shared library in Jenkinsfile?

Given this Jenkinsfile snippet:

library('my-shared-lib')
node {
  echo myFunction()
}

Assuming myFunction returns 'Hello from library!', what will Jenkins print?

Jenkins

library('my-shared-lib')
node {
  echo myFunction()
}

A myFunction

B Hello from library!

C Error: myFunction not found

D null

💡 Hint

The shared library loads functions that can be called directly in the Jenkinsfile.

The library step loads the shared library, making myFunction available. Calling it returns the string it defines.

❓ Configuration

intermediate

Which syntax correctly loads a shared library with a specific version in Jenkinsfile?

You want to load the shared library named utils at version 1.2.3. Which Jenkinsfile syntax is correct?

A library('utils@1.2.3')

B library(name: 'utils', version: '1.2.3')

C library('utils', '1.2.3')

D loadLibrary('utils', '1.2.3')

💡 Hint

The version is specified after an @ symbol in the library name string.

The correct syntax to load a specific version is library('name@version'). Other options are invalid or do not exist.

❓ Troubleshoot

advanced

Why does Jenkins fail to find the shared library function?

Given this Jenkinsfile:

library('common-lib')
node {
  echo greet()
}

And the shared library common-lib has a function greet defined in vars/greet.groovy.
Jenkins throws an error: groovy.lang.MissingMethodException: No signature of method: greet().
What is the most likely cause?

A The shared library is not configured in Jenkins global settings.

B The shared library version is missing in the library call.

C The function greet is not defined as a global variable in vars directory.

D The Jenkinsfile syntax for calling greet() is incorrect; it needs a prefix.

💡 Hint

Shared library functions must be in the vars directory to be called directly.

Functions in shared libraries must be placed in the vars directory as Groovy scripts to be accessible as global functions. If not, Jenkins cannot find them.

🔀 Workflow

advanced

What is the correct order to load and use a shared library in a Jenkins pipeline?

Arrange these steps in the correct order to use a shared library function in a Jenkinsfile:
1. Call the shared library function
2. Define the shared library in Jenkins global configuration
3. Load the shared library in Jenkinsfile
4. Create the shared library repository with functions

A 4,2,3,1

B 2,3,4,1

C 4,3,2,1

D 2,4,3,1

💡 Hint

Think about creating the library first, then configuring Jenkins, then loading and using it.

First, create the library repo with functions. Then configure Jenkins to know about it. Then load it in Jenkinsfile. Finally, call its functions.

✅ Best Practice

expert

Which approach is best to ensure shared library updates do not break Jenkins pipelines?

You maintain multiple Jenkins pipelines using a shared library. How do you best manage library updates to avoid breaking pipelines?

A Do not specify versions and rely on Jenkins global default library version.

B Always use the latest library version by calling library('lib@master') in Jenkinsfile.

C Update the shared library directly in Jenkins global config without version control.

D Use fixed library versions in Jenkinsfile and test updates in a separate branch before upgrading.

💡 Hint

Controlling versions and testing before upgrading helps avoid surprises.

Using fixed versions and testing updates in branches prevents unexpected breakage in pipelines when library code changes.