arjunsreepad/jenkins-cicd-pipeline-maven

JenkinsCI : Continious Delivery

---

This Delivery Pipeline extends the CI Pipeline implemented in the previous Lab. (07-jenkins-cicd-pipeline-maven-01-continious-integration). It adds the steps related to the deployment of the application in the Staging server, the performance analysis, and the promotion of the artificat to the release repository.

Required Setup for the Delivery Pipeline

Starting SonarQube and configuring the Web Hook

• Start the SonarQube Container

  docker run  --name my_sonarqube -p 9000:9000 sonarqube:lts  
  

  Connect to Sonarqube on http://localhost:9000 and check it is running

• Install the SonarQube Scanner plugin for Jenkins

• Configure the SonarQube server in Jenkins

  • Name: my_sonarqube_in_docker
  • Server URL: http://localhost:9000
  • Authentication: NONE Be sure that the Jenkins URL should be: http://localhost: 8080

• Back to SonarQube dashbooard and create a web hook to Jenkins

  • From "Administration" menu option, select "Configuration" option, then choose Web Hooks from its Dropdown
  • Configure the web hook
    • Give a name to the Web hook (for example my-webhook-to-jenkins)
    • URL: http://localhost:8080/sonarqube-webhook/ (Use strictly this form)
    • No need to fill in the secret as we are conversing anonymously with SonarQube.

Starting Nexus et Creating a Repository and User

• Start the SonarQube Container

  docker run -d --name my_nexus3 -p 8081:8081 sonatype/nexus3  

  Connect to Nexus on http://localhost:8081 and check it is running.

  You have to login in order to administer Nexus. The default username is admin, whereas to retrieve the password you need to run the following command:

  docker exec -i my_nexus3 cat /nexus-data/admin.password

  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 Snapshot repository in Nexus, where your Jenkins is going to upload "Snapshot" artifacts.

  • Follow the below-mentioned steps to create a hosted repository, name it as mylocalrepo-snapshots.

    

    In Version Policy, select the Snapshot type of artifacts.

  • Under the Hosted section, in Deployment policy, select Allow redeploy. It will allow you to deploy an application multiple times.

• Create a new User for the repository 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: In the Create User page,

  • ID: Enter the desired ID; in our case, it is jenkins-user.
  • First Name: Enter the desired first name; in our case, it is Jenkins.
  • Last Name: Enter the desired second name; in our case, it is User.
  • Email: Enter your email address.
  • Status: Select Active from your drop-down menu.
  • 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.

• 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 and Pipeline Utility Steps.

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

The Delivery pipeline

This is the stages of the Delivery pipeline:

• Clone App from Git
• Build and Unit Test (Maven/JUnit)
• Static Code Analysis (SonarQube)
• Checking the Quality Gate
• Integration Test (Maven/JUnit)
• Publish to Nexus Repository Manager
• Start the Staging Server
• Deploy the app on the staging
• Do the Performance Testing
• Publish the performance reports
• Promote the app in Nexus Repository Manager
• Clean Up : Stop the Stagin Server

The figure below shows the stages of the pipeline.