Artifact fingerprinting in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of artifact fingerprinting in Jenkins?

Artifact fingerprinting helps Jenkins track files across builds. What is its main benefit?

A To uniquely identify and track artifacts across different builds and jobs

B To compress artifacts to save disk space on the Jenkins server

C To encrypt artifacts for secure storage

D To automatically deploy artifacts to production servers

💡 Hint

Think about how Jenkins knows if the same file was used in multiple builds.

Artifact fingerprinting creates a unique hash for each artifact, allowing Jenkins to track where and when the artifact was used across builds and jobs.

💻 Command Output

intermediate

What output does Jenkins show after fingerprinting an artifact?

After enabling fingerprinting on a file in a Jenkins job, what information will Jenkins display about the artifact?

A The artifact's source code content

B The file size and last modified date only

C A unique hash value and a list of builds where the artifact was used

D The Jenkins server's IP address

💡 Hint

Fingerprinting is about tracking usage, not file details like size or content.

Jenkins shows a unique hash (fingerprint) for the artifact and lists all builds and jobs that used it, helping track artifact usage.

❓ Configuration

advanced

How to configure artifact fingerprinting in a Jenkins Pipeline script?

Which snippet correctly fingerprints an artifact file named app.jar in a Jenkins Pipeline?

A fingerprint 'app.jar'

B archiveArtifacts fingerprint: true, artifacts: 'app.jar'

C fingerprint artifacts: 'app.jar'

D archiveArtifacts 'app.jar', fingerprint: true

💡 Hint

Look for the correct syntax to archive and fingerprint artifacts in Pipeline.

The archiveArtifacts step archives files and can fingerprint them using the fingerprint: true option. The correct syntax is archiveArtifacts 'app.jar', fingerprint: true.

❓ Troubleshoot

advanced

Why does Jenkins fail to fingerprint an artifact in a freestyle job?

You enabled fingerprinting on a file in a freestyle job, but Jenkins does not show any fingerprint data after the build. What is the most likely cause?

A The artifact file was not archived during the build

B The Jenkins server is offline

C Fingerprinting is only supported in Pipeline jobs

D The artifact file is too large to fingerprint

💡 Hint

Fingerprinting requires the artifact to be saved by Jenkins first.

Fingerprinting works on archived artifacts. If the file is not archived, Jenkins cannot fingerprint it.

🔀 Workflow

expert

In a multi-job Jenkins workflow, how does artifact fingerprinting help with traceability?

Consider a workflow where Job A builds an artifact, and Job B uses it. How does fingerprinting improve traceability between these jobs?

A Fingerprinting deletes old artifacts after Job B completes

B Fingerprinting links the artifact's unique hash from Job A to Job B, showing artifact usage across jobs

C Fingerprinting automatically copies the artifact from Job A to Job B's workspace

D Fingerprinting encrypts the artifact to prevent unauthorized access between jobs

💡 Hint

Think about how Jenkins tracks the same file used in different jobs.

Fingerprinting creates a unique hash for the artifact in Job A and tracks its usage in Job B, providing clear traceability of artifact flow across jobs.

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