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.