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
            }
        }
    }
}

Need a 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..."'
            }
        }
    }
}

Need a 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
            }
        }
    }
}

Need a 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
            }
        }
    }
}

Need a hint?

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