External artifact repositories (Nexus, Artifactory) in Jenkins - Mini Project: Build & Apply

Using External Artifact Repositories with Jenkins

📖 Scenario: You are working as a DevOps engineer. Your team uses Jenkins to build software projects. You want to store build artifacts like JAR files in an external repository such as Nexus or Artifactory. This helps keep your builds organized and shareable.

🎯 Goal: Learn how to configure Jenkins to upload build artifacts to an external artifact repository (Nexus or Artifactory) using a simple Jenkins pipeline script.

📋 What You'll Learn

Create a Jenkins pipeline script with a build stage

Add a variable for the artifact repository URL

Use the sh step to simulate artifact upload command

Print a confirmation message after upload

💡 Why This Matters

🌍 Real World

Teams use Jenkins pipelines to automate building and uploading software artifacts to repositories like Nexus or Artifactory. This keeps builds organized and easy to share.

💼 Career

Knowing how to configure Jenkins with external artifact repositories is a key skill for DevOps engineers to manage software delivery pipelines efficiently.

1

Create a basic Jenkins pipeline with a build stage

Write a Jenkins pipeline script that defines a pipeline with an agent any and a stage named Build. Inside the stage, add a steps block with a shell command echo "Building project...".

Jenkins

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                // Your code here
            }
        }
    }
}

Hint

Use pipeline block with agent any. Inside stages, create a stage named Build. Use sh 'echo "Building project..."' inside steps.

2

Add a variable for the artifact repository URL

Add an environment variable called ARTIFACT_REPO_URL inside the pipeline block. Set its value to "http://nexus.example.com/repository/maven-releases/".

Jenkins

pipeline {
    agent any
    environment {
        // Your code here
    }
    stages {
        stage('Build') {
            steps {
                sh 'echo "Building project..."'
            }
        }
    }
}

Hint

Inside the pipeline block, add an environment block. Define ARTIFACT_REPO_URL with the exact URL string.

3

Simulate artifact upload using the repository URL

Inside the Build stage's steps, add a shell command that echoes Uploading artifact to $ARTIFACT_REPO_URL to simulate uploading the build artifact.

Jenkins

pipeline {
    agent any
    environment {
        ARTIFACT_REPO_URL = "http://nexus.example.com/repository/maven-releases/"
    }
    stages {
        stage('Build') {
            steps {
                sh 'echo "Building project..."'
                // Your code here
            }
        }
    }
}

Hint

Use another sh step after the build echo. Use echo "Uploading artifact to $ARTIFACT_REPO_URL" exactly.

4

Print a confirmation message after upload

Add a shell command inside the Build stage's steps that echoes Artifact upload completed successfully. to confirm the upload simulation.

Jenkins

pipeline {
    agent any
    environment {
        ARTIFACT_REPO_URL = "http://nexus.example.com/repository/maven-releases/"
    }
    stages {
        stage('Build') {
            steps {
                sh 'echo "Building project..."'
                sh 'echo "Uploading artifact to $ARTIFACT_REPO_URL"'
                // Your code here
            }
        }
    }
}

Hint

Use sh 'echo "Artifact upload completed successfully."' after the upload echo.

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