Why shared libraries reduce duplication in Jenkins - Visual Breakdown

Process Flow - Why shared libraries reduce duplication

Write shared library code

↓

Store in central repo

↓

Multiple Jenkinsfiles

↓

Reference shared library

↓

Reuse common code

↓

Less duplication, easier updates

Shared libraries hold common code in one place, so Jenkinsfiles can reuse it instead of copying code.

Execution Sample

Jenkins

@Library('my-shared-lib') _

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

This Jenkinsfile loads a shared library and calls a common step from it.

Process Table

Step	Action	Evaluation	Result
1	Load shared library 'my-shared-lib'	Library found in repo	Library code available
2	Start pipeline execution	Agent allocated	Pipeline running
3	Enter 'Build' stage	Stage recognized	Stage started
4	Call 'mySharedStep()' from library	Function found in shared lib	Shared code executed
5	Complete 'Build' stage	No errors	Stage finished
6	Pipeline ends	All stages done	Pipeline success

💡 Pipeline completes after running shared library code once

Status Tracker

Variable	Start	After Step 1	After Step 4	Final
libraryLoaded	false	true	true	true
pipelineStatus	not started	not started	running	success
sharedStepExecuted	false	false	true	true

Key Moments - 3 Insights

Why don't we see the shared library code inside the Jenkinsfile?

Because the Jenkinsfile references the shared library by name (see execution_table step 1), the actual code lives in the library repo and is loaded at runtime.

How does using a shared library reduce duplication?

Multiple Jenkinsfiles call the same shared library function (execution_table step 4), so common code is written once and reused, avoiding copy-pasting.

What happens if the shared library code changes?

All Jenkinsfiles using it get the updated code automatically next time they run, making maintenance easier (implied by execution_table steps 1 and 4).

Visual Quiz - 3 Questions

Look at the execution table, what is the state of 'libraryLoaded' after step 1?

A false

B true

C undefined

D error

💡 Hint

Check variable_tracker column 'After Step 1' for 'libraryLoaded'

At which step does the shared library code actually run?

A Step 4

B Step 1

C Step 2

D Step 6

💡 Hint

Look at execution_table 'Action' column for when 'mySharedStep()' is called

If the shared library was not loaded, what would happen at step 4?

A Pipeline runs normally

B Shared code runs anyway

C Error: function not found

D Pipeline skips the step

💡 Hint

Refer to execution_table step 4 where function is found in shared lib

Concept Snapshot

Shared libraries store common Jenkins pipeline code centrally.
Jenkinsfiles load libraries with 'library()' call.
They call shared functions instead of duplicating code.
This reduces errors and makes updates easy.
All pipelines using the library get improvements automatically.

Full Transcript

Shared libraries in Jenkins help reduce duplication by storing common pipeline code in one place. Jenkinsfiles load these libraries using the 'library()' function. When a Jenkinsfile calls a shared function, the code runs from the library, not copied inside the Jenkinsfile. This means many Jenkinsfiles can reuse the same code, avoiding repetition. If the shared library code changes, all Jenkinsfiles using it get the update automatically. This makes pipeline maintenance easier and less error-prone.