External artifact repositories (Nexus, Artifactory) in Jenkins - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is an external artifact repository like Nexus or Artifactory?

It is a storage system where built files (artifacts) like libraries or packages are saved and shared for use in software projects.

beginner

Why use an external artifact repository in Jenkins pipelines?

To store build outputs safely, share them with other teams, and manage versions easily without rebuilding everything from scratch.

intermediate

How does Jenkins interact with Nexus or Artifactory?

Jenkins uses plugins or scripts to upload (deploy) and download (fetch) artifacts during build and deployment steps.

beginner

What is a common format for artifacts stored in Nexus or Artifactory?

Common formats include JAR, WAR, ZIP, Docker images, and npm packages depending on the project type.

intermediate

What is the benefit of versioning artifacts in repositories like Nexus?

Versioning helps track changes, roll back to previous versions, and avoid conflicts between different builds or teams.

What is the main purpose of an external artifact repository?

A Monitor server health

B Run Jenkins pipelines

C Store and manage build artifacts

D Write source code

External artifact repositories store and manage build outputs for reuse and sharing.

Which Jenkins feature helps upload artifacts to Nexus or Artifactory?

A Build triggers

B Plugins or scripted steps

C Source code editor

D Test runners

Jenkins uses plugins or scripts to deploy artifacts to external repositories.

Which artifact format is NOT typically stored in Nexus or Artifactory?

A npm packages

B Docker images

C JAR files

D HTML web pages

HTML pages are usually served directly, not stored as artifacts in these repositories.

Why is artifact versioning important?

A To track and manage different builds

B To speed up Jenkins UI

C To write better code

D To monitor CPU usage

Versioning helps track changes and manage multiple artifact versions.

Which of these is a popular external artifact repository?

A Nexus

B GitHub

C Jenkins

D Docker Hub

Nexus is a widely used artifact repository; Jenkins is a CI tool, GitHub is for source code, Docker Hub is for container images.

Explain how Jenkins uses external artifact repositories like Nexus or Artifactory in a build pipeline.

Think about how Jenkins saves and retrieves files during builds.

Describe the benefits of using an external artifact repository in software development.

Consider how teams collaborate and reuse build outputs.

Practice

1. What is the main purpose of using external artifact repositories like Nexus or Artifactory in Jenkins pipelines?

easy

A. To monitor Jenkins job execution times

B. To run Jenkins jobs faster by caching source code

C. To replace Jenkins as a build server

D. To store and share build artifacts for reuse in other projects

Solution

1. Step 1: Understand artifact repositories role

   Artifact repositories store build outputs like binaries or libraries for reuse.

2. Step 2: Connect to Jenkins pipeline usage

   Jenkins uploads artifacts to these repositories to share with other projects or teams.

3. Final Answer:

   To store and share build artifacts for reuse in other projects -> Option D

4. Quick Check:

   Artifact repositories = store and share artifacts [OK]

Hint: Artifact repos store build outputs for sharing [OK]

Common Mistakes:

• Confusing artifact repos with build servers
• Thinking they speed up job execution directly
• Assuming they monitor Jenkins jobs

2. Which Jenkins plugin is commonly used to upload artifacts to a Nexus repository?

easy

A. Nexus Artifact Uploader

B. Git Plugin

C. Docker Pipeline

D. Slack Notification

Solution

1. Step 1: Identify plugins for artifact upload

   The Nexus Artifact Uploader plugin is designed to upload build artifacts to Nexus repositories.

2. Step 2: Exclude unrelated plugins

   Git Plugin manages source code, Docker Pipeline manages containers, Slack Notification sends messages.

3. Final Answer:

   Nexus Artifact Uploader -> Option A

4. Quick Check:

   Nexus upload plugin = Nexus Artifact Uploader [OK]

Hint: Nexus upload uses Nexus Artifact Uploader plugin [OK]

Common Mistakes:

• Choosing Git Plugin for artifact upload
• Confusing Docker Pipeline with artifact upload
• Selecting notification plugins by mistake

3. Given this Jenkins pipeline snippet using Artifactory plugin:

artifactoryServer.upload spec: '''{
  "files": [
    {"pattern": "build/libs/*.jar", "target": "libs-release-local/"}
  ]
}'''

What does this code do?

medium

A. Uploads all JAR files from build/libs to libs-release-local repository

B. Downloads JAR files from libs-release-local to build/libs

C. Deletes JAR files from build/libs directory

D. Builds JAR files inside the Jenkins workspace

Solution

1. Step 1: Analyze the upload spec JSON

   The spec says to upload files matching build/libs/*.jar to target libs-release-local/ repository.

2. Step 2: Understand Artifactory plugin upload method

   upload method sends files from Jenkins workspace to the external repository location.

3. Final Answer:

   Uploads all JAR files from build/libs to libs-release-local repository -> Option A

4. Quick Check:

   upload spec = upload files to repo [OK]

Hint: Upload spec means send files to repo path [OK]

Common Mistakes:

• Confusing upload with download
• Thinking it deletes files
• Assuming it builds artifacts

4. You configured Jenkins to upload artifacts to Nexus but the upload fails with authentication error. What is the most likely cause?

medium

A. Build artifacts are missing in workspace

B. Incorrect repository URL configured in Jenkins

C. Missing or wrong credentials for Nexus repository in Jenkins

D. Jenkins server is offline

Solution

1. Step 1: Understand authentication error meaning

   Authentication errors usually mean Jenkins cannot log in to Nexus due to bad credentials.

2. Step 2: Check common causes

   Incorrect URL causes connection errors, missing artifacts cause upload failure but not auth error, offline server causes connection failure.

3. Final Answer:

   Missing or wrong credentials for Nexus repository in Jenkins -> Option C

4. Quick Check:

   Auth error = bad credentials [OK]

Hint: Auth errors mean check credentials first [OK]

Common Mistakes:

• Assuming URL is always the cause
• Ignoring credentials setup
• Confusing missing files with auth errors

5. You want to configure a Jenkins pipeline to upload a Docker image to Artifactory and also store the build logs as an artifact. Which two configurations are essential?

hard

A. Configure Git repository URL; use 'docker build' only

B. Configure Artifactory Docker registry URL and credentials; use 'archiveArtifacts' step for logs

C. Use 'sh' step to upload logs manually; no credentials needed

D. Configure Jenkins email notifications; use 'stash' for Docker images

Solution

1. Step 1: Identify Docker image upload requirements

   Uploading Docker images to Artifactory requires setting the Docker registry URL and credentials in Jenkins.

2. Step 2: Identify artifact storage for logs

   Jenkins 'archiveArtifacts' step stores build logs or files as artifacts for later access.

3. Final Answer:

   Configure Artifactory Docker registry URL and credentials; use 'archiveArtifacts' step for logs -> Option B

4. Quick Check:

   Docker upload + archive logs = config URL/creds + archiveArtifacts [OK]

Hint: Docker upload needs registry + creds; logs need archiveArtifacts [OK]

Common Mistakes:

• Confusing Git URL with Docker registry URL
• Skipping credentials for Artifactory
• Using stash instead of archiveArtifacts for logs