External artifact repositories (Nexus, Artifactory) in Jenkins - Commands & Configuration

Introduction

When you build software, you create files called artifacts like libraries or packages. External artifact repositories like Nexus or Artifactory store these files safely so you can share and reuse them easily.

When you want to save your built software files in a central place for your team to use.

When you need to share libraries between different projects without copying files manually.

When you want to keep track of different versions of your software packages.

When you want to download third-party libraries automatically during your build process.

When you want to improve build speed by caching dependencies in a repository.

Config File - Jenkinsfile

Jenkinsfile

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        echo 'Building the project'
        // Simulate build step
      }
    }
    stage('Publish Artifact') {
      steps {
        script {
          def nexusUrl = 'http://nexus.example.com/repository/maven-releases/'
          def artifactPath = 'target/my-app-1.0.jar'
          sh "curl -u admin:admin123 --upload-file ${artifactPath} ${nexusUrl}my-app-1.0.jar"
        }
      }
    }
  }
}

This Jenkinsfile defines a simple pipeline with two stages: Build and Publish Artifact.

In the Publish Artifact stage, it uploads the built file to a Nexus repository using curl with authentication.

This shows how Jenkins can send artifacts to an external repository for storage and sharing.

Commands

This command uploads the built artifact file to the Nexus repository using curl with username and password authentication.

Terminal

curl -u admin:admin123 --upload-file target/my-app-1.0.jar http://nexus.example.com/repository/maven-releases/my-app-1.0.jar

Expected Output

No output (command runs silently)

→

-u admin:admin123 - Provides username and password for authentication

→

--upload-file target/my-app-1.0.jar - Specifies the file to upload

This command downloads the artifact from the Nexus repository to verify it was uploaded correctly.

Terminal

curl -u admin:admin123 http://nexus.example.com/repository/maven-releases/my-app-1.0.jar -O

Expected Output

No output (command runs silently)

→

-u admin:admin123 - Authentication credentials

→

-O - Saves the file with its original name

Key Concept

If you remember nothing else from this pattern, remember: external artifact repositories safely store and share your build files so teams can reuse and manage software versions easily.

Common Mistakes

Uploading artifacts without authentication or with wrong credentials

The repository will reject the upload and the artifact won't be saved.

Always provide correct username and password or token when uploading artifacts.

Not verifying the artifact upload by downloading or checking the repository

You might think the upload succeeded but the artifact could be missing or corrupted.

After upload, download the artifact or check the repository UI to confirm it is stored.

Summary

Use curl with authentication to upload build artifacts to Nexus or Artifactory repositories.

Verify artifact upload by downloading the file or checking the repository UI.

Configure Jenkins pipelines to automate artifact publishing to external repositories.

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