Why artifact management matters in Jenkins - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a Jenkins pipeline stage that archives build artifacts.

Jenkins

stage('Archive Artifacts') {
    steps {
        [1] 'build/output/*.jar'
    }
}

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

Ash

BarchiveArtifacts

Ccheckout

Decho

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'sh' instead of 'archiveArtifacts' to save files.

The archiveArtifacts step in Jenkins saves build outputs so they can be accessed later.

2fill in blank

medium

Complete the code to upload an artifact to a Nexus repository using a shell command in Jenkins.

Jenkins

stage('Upload Artifact') {
    steps {
        sh 'curl -v -u user:pass -X POST [1]'
    }
}

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

A"http://nexus.example.com/repository/maven-snapshots/" -F 'file=app.jar'

B"http://nexus.example.com/repository/maven-releases/" -d 'file=app.jar'

C"http://nexus.example.com/repository/maven-releases/" -F 'file=@build/output/app.jar'

D"http://nexus.example.com/repository/maven-releases/" -F 'file=app.jar'

Attempts:

3 left

💡 Hint

Common Mistakes

Using '-d' instead of '-F' to upload files.

The curl command uploads the artifact file to the Nexus repository using the -F flag for form data.

3fill in blank

hard

Fix the error in the Jenkins pipeline snippet that tries to download an artifact but uses the wrong step.

Jenkins

stage('Download Artifact') {
    steps {
        [1] 'curl -O http://nexus.example.com/repository/maven-releases/app.jar'
    }
}

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

Ash

BdownloadArtifacts

CarchiveArtifacts

Dcheckout

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'archiveArtifacts' to download files.

The sh step runs shell commands. To download an artifact, you can use curl inside sh. There is no built-in downloadArtifacts step.

4fill in blank

hard

Fill both blanks to create a Jenkins pipeline snippet that saves and then cleans up artifacts.

Jenkins

stage('Save and Clean') {
    steps {
        [1] 'dist/*.zip'
        [2]()
    }
}

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

AarchiveArtifacts

Bsh

CdeleteDir

Dcheckout

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'sh' to delete directories instead of 'deleteDir'.

archiveArtifacts saves the files, and deleteDir cleans the workspace directory.

5fill in blank

hard

Fill all three blanks to define a Jenkins pipeline that builds, archives, and uploads an artifact.

Jenkins

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                [1] 'mvn clean package'
            }
        }
        stage('Archive') {
            steps {
                [2] 'target/*.jar'
            }
        }
        stage('Upload') {
            steps {
                [3] 'curl -v -u user:pass -X POST "http://nexus.example.com/repository/maven-releases/" -F "file=@target/app.jar"'
            }
        }
    }
}

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

Ash

BarchiveArtifacts

Dcheckout

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'checkout' instead of 'sh' for build or upload steps.

Use sh to run the build command, archiveArtifacts to save the jar, and sh again to upload with curl.

Practice

1. Why is artifact management important in Jenkins pipelines?

easy

A. It automatically deletes all build files after each run.

B. It saves build files for reuse and sharing across jobs.

C. It slows down the build process by adding extra steps.

D. It only works with Docker containers, not regular files.

Solution

1. Step 1: Understand artifact management purpose

   Artifact management stores build outputs so they can be reused without rebuilding.

2. Step 2: Identify correct Jenkins behavior

   Jenkins pipelines use artifact management to save and share files, improving efficiency.

3. Final Answer:

   It saves build files for reuse and sharing across jobs. -> Option B

4. Quick Check:

   Artifact management = saves and shares files [OK]

Hint: Artifacts store build files for reuse, not deletion [OK]

Common Mistakes:

• Thinking artifacts delete files after build
• Believing artifact management slows builds
• Assuming artifacts only work with Docker

2. Which Jenkins pipeline step syntax correctly archives artifacts?

easy

A. archiveArtifacts 'build/output/*.jar'

B. archive 'build/output/*.jar'

C. saveArtifacts 'build/output/*.jar'

D. storeArtifacts 'build/output/*.jar'

Solution

1. Step 1: Recall Jenkins pipeline syntax

   The correct step to archive artifacts is archiveArtifacts.

2. Step 2: Match syntax with options

   Only archiveArtifacts 'build/output/*.jar' uses the exact Jenkins step archiveArtifacts with correct string pattern.

3. Final Answer:

   archiveArtifacts 'build/output/*.jar' -> Option A

4. Quick Check:

   Correct step is archiveArtifacts [OK]

Hint: Use archiveArtifacts to save files in Jenkins [OK]

Common Mistakes:

• Using archive instead of archiveArtifacts
• Using saveArtifacts or storeArtifacts which don't exist
• Missing quotes around file pattern

3. What will Jenkins display after running this pipeline snippet?

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

medium

A. Build succeeds but no artifacts are saved.

B. Build fails due to missing artifact directory.

C. Build succeeds and output.txt is saved as an artifact.

D. Build fails because archiveArtifacts is not a valid step.

Solution

1. Step 1: Analyze pipeline steps

   The shell command creates a file named output.txt. Then archiveArtifacts saves it.

2. Step 2: Understand Jenkins behavior

   Jenkins archives the file successfully, so build passes and artifact is saved.

3. Final Answer:

   Build succeeds and output.txt is saved as an artifact. -> Option C

4. Quick Check:

   File created and archived = success [OK]

Hint: archiveArtifacts saves files created in build steps [OK]

Common Mistakes:

• Assuming archiveArtifacts needs a directory
• Thinking archiveArtifacts causes build failure
• Believing artifacts are not saved automatically

4. A Jenkins pipeline fails to save artifacts with this step:

archiveArtifacts build/output/*.jar

What is the likely cause?

medium

A. Jenkins cannot archive .jar files.

B. The archiveArtifacts step does not exist.

C. The build/output directory does not exist.

D. Missing quotes around the file pattern.

Solution

1. Step 1: Check syntax for archiveArtifacts

   The file pattern must be a string, so it needs quotes.

2. Step 2: Identify error cause

   Without quotes, Jenkins treats the pattern as a command or variable, causing failure.

3. Final Answer:

   Missing quotes around the file pattern. -> Option D

4. Quick Check:

   File pattern needs quotes [OK]

Hint: Always quote file patterns in archiveArtifacts [OK]

Common Mistakes:

• Forgetting quotes around file patterns
• Assuming archiveArtifacts is invalid
• Blaming Jenkins for unsupported file types

5. You want to reuse a build artifact from a previous Jenkins job in a new pipeline. Which approach best ensures artifact availability and reuse?

hard

A. Archive artifacts in the first job and use the Copy Artifact plugin in the new job.

B. Rebuild the artifact every time to avoid stale files.

C. Store artifacts only on the local workspace without archiving.

D. Send artifacts via email between jobs.

Solution

1. Step 1: Understand artifact reuse in Jenkins

   Archiving artifacts saves them for later retrieval by other jobs.

2. Step 2: Identify best method for sharing artifacts

   The Copy Artifact plugin allows a job to fetch archived artifacts from another job safely.

3. Final Answer:

   Archive artifacts in the first job and use the Copy Artifact plugin in the new job. -> Option A

4. Quick Check:

   Archive + Copy Artifact plugin = reuse [OK]

Hint: Use archiveArtifacts + Copy Artifact plugin for sharing [OK]

Common Mistakes:

• Rebuilding artifacts wastes time
• Not archiving loses artifact history
• Using email is unreliable and manual