Artifact fingerprinting in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable fingerprinting for the artifact in a Jenkins pipeline.

Jenkins

fingerprint '[1]'

Drag options to blanks, or click blank then click option'

Abuild.log

Btarget/*.jar

CREADME.md

DDockerfile

Attempts:

3 left

💡 Hint

Common Mistakes

Fingerprinting a log file instead of the artifact

Using a file that does not exist in the build workspace

Using fingerprint 'target/*.jar' tells Jenkins to fingerprint all JAR files in the target directory, which are typical build artifacts.

2fill in blank

medium

Complete the code to archive and fingerprint the artifact in a Jenkins pipeline.

Jenkins

archiveArtifacts artifacts: '[1]', fingerprint: true

Drag options to blanks, or click blank then click option'

Abuild.log

Bdocs/*.md

Ctarget/*.jar

Dsrc/**/*.java

Attempts:

3 left

💡 Hint

Common Mistakes

Archiving source code files instead of build artifacts

Not enabling fingerprinting by setting fingerprint: true

Archiving and fingerprinting the JAR files in the target directory ensures the artifacts are saved and tracked.

3fill in blank

hard

Fix the error in the fingerprint step to correctly fingerprint the artifact.

Jenkins

fingerprint [1]

Drag options to blanks, or click blank then click option'

A'target/*.jar'

Btarget/*.jar

C"target/*.jar"

D['target/*.jar']

Attempts:

3 left

💡 Hint

Common Mistakes

Not quoting the file pattern

Using a list instead of a string for the pattern

The fingerprint step requires the file pattern as a quoted string. Using single quotes is standard in Jenkins pipelines.

4fill in blank

hard

Fill both blanks to archive and fingerprint multiple artifact types in a Jenkins pipeline.

Jenkins

archiveArtifacts artifacts: '[1]', fingerprint: [2]

Drag options to blanks, or click blank then click option'

Atarget/*.jar, target/*.war

Btrue

Cfalse

Dtarget/*.zip

Attempts:

3 left

💡 Hint

Common Mistakes

Using a list instead of a comma-separated string for artifacts

Setting fingerprint to false or omitting it

To archive multiple artifact types, list them separated by commas as a string. Setting fingerprint: true enables fingerprinting.

5fill in blank

hard

Fill all three blanks to create a fingerprint for a specific artifact, archive it, and print a confirmation message.

Jenkins

fingerprint '[1]'
archiveArtifacts artifacts: '[2]', fingerprint: true
println '[3] created and fingerprinted.'

Drag options to blanks, or click blank then click option'

Atarget/app.jar

CArtifact

Dtarget/app.zip

Attempts:

3 left

💡 Hint

Common Mistakes

Using different artifact names in fingerprint and archive steps

Printing a message without context

This code fingerprints and archives the target/app.jar artifact, then prints a confirmation message using the word 'Artifact'.

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