Publishing Artifacts to Sonatype Nexus using Jenkins Pipelines
Tags: docker, devops
Published: 2020-08-07 09:43:23

In this guide, we will use Jenkins as a Continuous Integration server and Nexus as a build repository. 

The end goal of this guide is to create a flow, where we can build, store, organize and monitor the compiled artifacts by Maven through our CI server.

Before we begin, make sure that you already have Jenkins up and running. In case you haven’t set up Jenkins yet, then copy the below command and run it on your Docker enabled host/machine.

```
$ docker run -d --name jenkins-ci -p 8080:8080 jenkins/jenkins:lts
```

Once, Jenkins container is configured on your local/remote machine. Go to your preferred browser and open the URL `http:///your-ip-addr:8080`. 

On the very first page, Jenkins will ask you for the admin password, which you can find by running below mentioned command in your terminal:
```
$  docker exec -i jenkins-ci cat /var/jenkins_home/secrets/initialAdminPassword

b5102c8d9fa245dbb0b8da03f504d3a5
```

Follow the guided steps to finish the configuration. Save the username and password securely for future use.

##Installing Nexus:

Nexus is a repository manager that allows you to store and retrieve artifacts. It enables you to host your built artifacts in a private and secure repo. You can always pull the Nexus Docker image using the following command:

```
$ docker pull sonatype/nexus3
 
Using default tag: latest
latest: Pulling from sonatype/nexus3
cb3c77f9bdd8: Pull complete 
fd8daf2668d1: Pull complete 
fd1ff82b00e8: Pull complete 
2a05f7b573af: Pull complete 
Digest: sha256:6570855dfbc3eb094fe5cbbacec87aa8b91d16394dab627177e1deeebb5ac8ee
Status: Downloaded newer image for sonatype/nexus3:latest
docker.io/sonatype/nexus3:latest
```

Now it’s time to run downloaded `sonatype/nexus` on the default port `8081`. Follow the below-mentioned commands:

```
$ docker run -d --name nexus_repo -p 8081:8081 sonatype/nexus3
```

Usually it takes 1 to 2 minutes for the Nexus service to launch in your newly created Docker container. If you wish to follow the log to see if Nexus is up and ready, then run the following command:

```
$ docker logs nexus_repo -f 
```

In logs you will see a message stating `Started Sonatype Nexus OSS 3.20.1-01`. It means your Nexus Repository Manager is ready to use. Now go to your browser and open `http://your-ip-addr:8081`. Find the *Sign In* option as shown below:

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/i/spgp514896mz6pv6hz4f.png)

The default username is admin, whereas to retrieve the password you need to run the following command:
```
$ docker exec -i nexus_repo cat /nexus-data/admin.password
502ace93-5450-4f0d-97d2-9b3b3a88d149
```

And that’s it. Your Nexus Repository Manager is ready-to-use. The next step is to create a new repository.

##Create a Repository in Nexus:

In this step, you are going to create a Maven Hosted repository in Nexus, where your Jenkins is going to upload “build” artifacts.

**Step 1:**
Follow the below-mentioned steps to create a hosted repository, name it as `maven-nexus-repo`, which you are going to use throughout this guide.

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/i/z6t4fhd4kswm1h8a2aks.png)

Select *maven2 (hosted)* recipe from the list as shown in the below-mentioned figure:

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/i/6goetyppvus4wfdzxmqe.png)

**Step 2:**
On the *Create Repository* page, 
* Enter the name as *maven-nexus-repo*
* In Version Policy, select the *Mixed* type of artifacts.
* Under the *Hosted* section, in *Deployment policy*, select *Allow redeploy*. It will allow you to deploy an application multiple times.

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/i/8jq4pc5vdpu9a5tmkrz3.png)

**Step 3:**
To create a new user, go to *Dashboard > Server Administrator and Configuration > User > Create user*. Select *Local* user type which happens to be the default Realm:

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/i/nh28chsv1gz9wzw6mqrx.png)

In the *Create User* page,
1.**ID**: Enter the desired ID; in our case, it is `jenkins-user`.
2.**First Name**: Enter the desired first name; in our case, it is `Jenkins`.
3.**Last Name**: Enter the desired second name; in our case, it is `User`.
4.**Email**: Enter your email address.
5.**Status**: Select *Active* from your drop-down menu.
6.**Roles**: Make sure that you grant the *nx-admin* role to your user.

In case you want more details for user creation, then click [here](https://help.sonatype.com/repomanager3/security/users).

With this, we are through with the setup part of Nexus Repository Manager. Let us move to Jenkins to setup Nexus there.

##Install and Configure Nexus Plugins in Jenkins

Here you are going to install and configure a few plugins for Nexus in Jenkins. For this, go to Jenkins and then *Dashboard > Manage Jenkins > Manage Plugins > Available* and search and install [*Nexus Artifact Uploader*](https://plugins.jenkins.io/nexus-artifact-uploader) and [*Pipeline Utility Steps*](https://plugins.jenkins.io/pipeline-utility-steps).

Add Nexus Repository Manager’s user credentials in Jenkins. Go to *Dashboard > Credentials > System > Global credentials (unrestricted)*, as shown below:

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/i/9k2bshq0hwiwecrt196z.png)

Next, set up Maven as a managed tool. Go to *Dashboard > Manage Jenkins > Global Tool Configuration* and find *Maven*. Under this section, click on the *Maven Installations* button and add *Maven*, as shown below:

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/i/bo6gsxadqykob6yd5det.png)

Alternatively, you can also install the Maven binary directly to your container on the `/var/jenkins_home` directory.

##Create a Jenkins Pipeline

It’s time to create a Jenkins Job. Here you are going to use Pipeline job type, named as *JenkinsNexus*, as shown below:

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/i/wkl40ppetc4qhgezw0ne.png)

In the next page, find the Pipeline section and copy the below-mentioned script in the text area:

```
pipeline {
    agent {
        label "master"
    }
    tools {
        maven "Maven"
    }
    environment {
        NEXUS_VERSION = "nexus3"
        NEXUS_PROTOCOL = "http"
        NEXUS_URL = "you-ip-addr-here:8081"
        NEXUS_REPOSITORY = "maven-nexus-repo"
        NEXUS_CREDENTIAL_ID = "nexus-user-credentials"
    }
    stages {
        stage("Clone code from VCS") {
            steps {
                script {
                    git 'https://github.com/javaee/cargotracker.git';
                }
            }
        }
        stage("Maven Build") {
            steps {
                script {
                    sh "mvn package -DskipTests=true"
                }
            }
        }
        stage("Publish to Nexus Repository Manager") {
            steps {
                script {
                    pom = readMavenPom file: "pom.xml";
                    filesByGlob = findFiles(glob: "target/*.${pom.packaging}");
                    echo "${filesByGlob[0].name} ${filesByGlob[0].path} ${filesByGlob[0].directory} ${filesByGlob[0].length} ${filesByGlob[0].lastModified}"
                    artifactPath = filesByGlob[0].path;
                    artifactExists = fileExists artifactPath;
                    if(artifactExists) {
                        echo "*** File: ${artifactPath}, group: ${pom.groupId}, packaging: ${pom.packaging}, version ${pom.version}";
                        nexusArtifactUploader(
                            nexusVersion: NEXUS_VERSION,
                            protocol: NEXUS_PROTOCOL,
                            nexusUrl: NEXUS_URL,
                            groupId: pom.groupId,
                            version: pom.version,
                            repository: NEXUS_REPOSITORY,
                            credentialsId: NEXUS_CREDENTIAL_ID,
                            artifacts: [
                                [artifactId: pom.artifactId,
                                classifier: '',
                                file: artifactPath,
                                type: pom.packaging],
                                [artifactId: pom.artifactId,
                                classifier: '',
                                file: "pom.xml",
                                type: "pom"]
                            ]
                        );
                    } else {
                        error "*** File: ${artifactPath}, could not be found";
                    }
                }
            }
        }
    }
}
```

Let’s break down the above-mentioned parameters bit by bit:
* **NEXUS_VERSION**: Here, we have to mention the exact version of Nexus, which can be `nexus2` or `nexus3`. In our case, it is latest version of `nexus3`.
* **NEXUS_PROTOCOL**: For this guide we have used HTTP protocol, although, in case of production, you will have to use HTTPS.
* **NEXUS_URL**: Add your IP address and port number, where you are running Nexus. Make sure that you add Nexus instance details without mentioning protocols, i.e., `https` or `http`.
* **NEXUS_CREDENTIAL_ID**: Enter the user ID, which you previously created in Jenkins, which in our case is `nexus-user-credentials`.
* **Project Git**: Under stages, we used `https://github.com/javaee/cargotracker`

As you are through with the Pipeline set up, it’s time to `Build` our project. Go to the *JenkinsNexus* project job page and click *Build Now*. As this is your first build, it is going to take some time, so sit tight.

Once build is a success, in your Jenkins Console Output, you will see something like this:

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/i/toeu4fp80x3bp5tbp1ms.png)

Whereas, in your Nexus Repository Manager, you would see something similar to this:

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/i/fx5xftbvgg3zjcr065rc.png)

**Conclusion:**

A systematic way to disturb the project’s artifact is critical for any organization. With the help of Jenkins Pipeline and Nexus Repository Manager, you can centralize artifact repo, which ultimately reduces the efforts of reproducing build time as well as switch CI tools without worrying about migrating our artifacts.

Nexus can be configured with cloud storage services like AWS S3 and Google Cloud Storage as well, which gives you additional freedom and delivery application without any hassle of storage.