External artifact repositories (Nexus, Artifactory) in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the Jenkins pipeline code to upload an artifact to Nexus.

Jenkins

sh 'curl -v -u admin:admin123 -X POST "http://nexus.example.com/repository/maven-releases/" -F "r=releases" -F "hasPom=false" -F "e=jar" -F "file=[1]"'

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

Apom.xml

Bsrc/main/java

CREADME.md

Dtarget/my-app.jar

Attempts:

3 left

💡 Hint

Common Mistakes

Using source code folder instead of the built artifact.

Uploading the pom.xml instead of the jar file.

The artifact file to upload is the built jar file, usually located in the target/ directory.

2fill in blank

medium

Complete the Jenkins pipeline snippet to download an artifact from Artifactory using curl.

Jenkins

sh 'curl -u user:password -O http://artifactory.example.com/artifactory/libs-release-local/[1]'

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

Abuild.gradle

Bsrc/main/resources/config.yaml

Ccom/example/my-app/1.0/my-app-1.0.jar

Ddocs/manual.pdf

Attempts:

3 left

💡 Hint

Common Mistakes

Using source files or documentation instead of the artifact jar.

Incorrect artifact path format.

The artifact path in Artifactory includes group, artifact name, version, and file name.

3fill in blank

hard

Fix the error in this Jenkins pipeline step to publish to Nexus by completing the missing option.

Jenkins

sh 'mvn deploy:deploy-file -Durl=http://nexus.example.com/repository/maven-releases/ -DrepositoryId=[1] -Dfile=target/app.jar -DgroupId=com.example -DartifactId=app -Dversion=1.0 -Dpackaging=jar'

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

Anexus

Breleases

Ccentral

Dsnapshots

Attempts:

3 left

💡 Hint

Common Mistakes

Using repository names like 'central' which is Maven Central, not Nexus.

Using 'releases' or 'snapshots' which are repository names, not repository IDs.

The -DrepositoryId must match the server ID configured in Maven settings for Nexus credentials.

4fill in blank

hard

Fill both blanks to configure Jenkins to use Artifactory plugin for uploading artifacts.

Jenkins

def server = Artifactory.server('[1]')
server.upload spec: '''{
  "files": [
    {"pattern": "build/libs/*.jar", "target": "[2]"}
  ]
}'''

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

Aartifactory-server

Blibs-release-local

Clibs-snapshot-local

Ddocker-local

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing server ID with repository name.

Using snapshot repository for release artifacts.

The server name matches the Jenkins Artifactory server configuration ID, and the target is the repository name in Artifactory.

5fill in blank

hard

Fill all three blanks to define a Jenkins pipeline step that downloads a specific artifact from Nexus using curl.

Jenkins

sh 'curl -u [1]:[2] -O http://nexus.example.com/repository/[3]/com/example/app/1.0/app-1.0.jar'

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

Aadmin

Badmin123

Cmaven-releases

Dmaven-snapshots

Attempts:

3 left

💡 Hint

Common Mistakes

Using snapshot repository for release artifact download.

Incorrect or missing credentials causing authentication failure.

The username and password are for Nexus authentication, and the repository is the release repository where the artifact is stored.

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