Artifact fingerprinting in Jenkins - Time & Space Complexity

Time Complexity: Artifact fingerprinting

O(n)

Understanding Time Complexity

We want to understand how the time needed to fingerprint artifacts grows as we handle more files.

How does the process scale when the number of artifacts increases?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

pipeline {
  agent any
  stages {
    stage('Fingerprint Artifacts') {
      steps {
        fingerprint '**/*.jar'
      }
    }
  }
}
    

This pipeline fingerprints all jar files found in the workspace to track their usage.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Scanning and fingerprinting each matching artifact file.
• How many times: Once for each jar file found in the workspace.

How Execution Grows With Input

As the number of jar files increases, the fingerprinting work grows proportionally.

Input Size (n)	Approx. Operations
10	10 fingerprint operations
100	100 fingerprint operations
1000	1000 fingerprint operations

Pattern observation: The time grows directly with the number of files; doubling files doubles work.

Final Time Complexity

Time Complexity: O(n)

This means the time to fingerprint grows in a straight line with the number of artifacts.

Common Mistake

[X] Wrong: "Fingerprinting all files takes the same time no matter how many files there are."

[OK] Correct: Each file must be processed separately, so more files mean more time.

Interview Connect

Understanding how fingerprinting scales helps you explain build pipeline performance clearly and confidently.

Self-Check

"What if we fingerprinted only changed files instead of all files? How would the time complexity change?"

Practice

1. What is the main purpose of artifact fingerprinting in Jenkins?

easy

A. To uniquely track files across different builds

B. To speed up the build process

C. To automatically deploy artifacts to servers

D. To create backups of build logs

Solution

1. Step 1: Understand artifact fingerprinting concept

   Artifact fingerprinting is used to track files uniquely across Jenkins builds.

2. Step 2: Identify the main purpose

   Its main purpose is to know where files come from and where they are used, not speeding builds or deployment.

3. Final Answer:

   To uniquely track files across different builds -> Option A

4. Quick Check:

   Artifact fingerprinting = Unique file tracking [OK]

Hint: Fingerprinting tracks files uniquely across builds [OK]

Common Mistakes:

• Confusing fingerprinting with deployment
• Thinking it speeds up builds
• Assuming it backs up logs

2. Which Jenkins pipeline step is used to enable artifact fingerprinting for a file?

easy

A. archiveArtifacts 'file.txt'

B. publish 'file.txt'

C. stash 'file.txt'

D. fingerprint 'file.txt'

Solution

1. Step 1: Recall Jenkins pipeline steps for artifacts

   Common steps include archiveArtifacts, stash, fingerprint, and publish.

2. Step 2: Identify the step for fingerprinting

   The fingerprint step is specifically used to enable artifact fingerprinting on files.

3. Final Answer:

   fingerprint 'file.txt' -> Option D

4. Quick Check:

   Use fingerprint step to track files [OK]

Hint: Use fingerprint step with file path to track [OK]

Common Mistakes:

• Using archiveArtifacts instead of fingerprint
• Confusing stash with fingerprint
• Using publish which is unrelated

3. Given this Jenkins pipeline snippet:

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        sh 'echo Hello > output.txt'
        fingerprint 'output.txt'
      }
    }
  }
}

What does the fingerprint 'output.txt' step do here?

medium

A. Deletes output.txt after the build

B. Creates a unique hash for output.txt to track it across builds

C. Copies output.txt to the workspace

D. Uploads output.txt to a remote server

Solution

1. Step 1: Analyze the pipeline snippet

   The pipeline creates a file output.txt and then fingerprints it.

2. Step 2: Understand fingerprint step effect

   The fingerprint step creates a unique hash for the file to track it across builds, not deleting or copying it.

3. Final Answer:

   Creates a unique hash for output.txt to track it across builds -> Option B

4. Quick Check:

   Fingerprint = unique hash tracking [OK]

Hint: Fingerprint creates unique hash for file tracking [OK]

Common Mistakes:

• Thinking fingerprint deletes files
• Assuming it copies files
• Confusing fingerprint with upload

4. You added fingerprint 'app.jar' in your Jenkins pipeline, but fingerprints are not generated. What is a likely cause?

medium

A. You must archive artifacts before fingerprinting

B. Fingerprinting requires a separate plugin installation

C. The file path 'app.jar' is incorrect or file does not exist

D. Fingerprinting only works on text files

Solution

1. Step 1: Check file existence for fingerprinting

   Fingerprinting requires the file to exist at the specified path during the build.

2. Step 2: Identify common causes for no fingerprints

   If the file path is wrong or file missing, fingerprinting won't generate fingerprints.

3. Final Answer:

   The file path 'app.jar' is incorrect or file does not exist -> Option C

4. Quick Check:

   File must exist for fingerprinting [OK]

Hint: Ensure file exists at path before fingerprinting [OK]

Common Mistakes:

• Assuming fingerprint needs extra plugin
• Thinking archiveArtifacts is mandatory before fingerprint
• Believing fingerprint only works on text files

5. In a Jenkins pipeline, you want to track multiple artifacts and find all builds that used them. Which approach correctly uses artifact fingerprinting for this?

hard

A. Use fingerprint '**/*.jar' after building all jar files

B. Archive artifacts first, then fingerprint only one file manually

C. Use stash for all files and fingerprint none

D. Fingerprint files only in the first build, skip others

Solution

1. Step 1: Understand tracking multiple artifacts

   To track multiple files, fingerprinting should be applied to all relevant files, e.g., using a pattern.

2. Step 2: Evaluate options for multiple files

   Using fingerprint '**/*.jar' fingerprints all jar files, enabling tracking across builds.

3. Final Answer:

   Use fingerprint '**/*.jar' after building all jar files -> Option A

4. Quick Check:

   Fingerprint all files with pattern for tracking [OK]

Hint: Fingerprint all files with a pattern to track multiple artifacts [OK]

Common Mistakes:

• Fingerprinting only one file when multiple exist
• Confusing stash with fingerprinting
• Skipping fingerprinting in later builds