hands-on lab

Create a Jenkins CICD Pipeline to Publish Build Results into Jira

Difficulty: Intermediate

Duration: Up to 2 hours

Students: 1,144

Rating: 4.5/5

Start lab

Get guided in a real environmentPractice with a step-by-step scenario in a real, provisioned environment.

Learn and validateUse validations to check your solutions every step of the way.

See resultsTrack your knowledge and monitor your progress.

Description

Lab Overview

Integrating Jenkins and Jira together provides you with a solution that can be used to report issues as they happen for any CICD pipeline build job. Jenkins can be configured to publish any and all build results, artifacts, and/or bugs directly into Jira. DevOps teams can then use Jira to project manage the required fixes necessary to get their applications into production.

In this lab, you will launch a Jenkins and Jira CICD and issue management environment using Docker containers on a provided EC2 instance. You will then configure a Jenkins build pipeline to build, compile, and package a sample Java servlet web application, with the resulting build information being published automatically into Jira. You will then use Jira to observe the details about the Jenkins build just performed.

This lab is aimed at DevOps and CICD practitioners, and, in particular, build and release engineers interested in managing and configuring Jenkins together with Jira for enterprise-grade issue tracking.

Note: To complete this lab, you will be required to generate a trial license on the Atlassian website, which is used to activate the Jira application. This will require you to either have an existing Atlassian user account or create a new Atlassian user account.

Lab Objectives

Upon completion of this lab, you will be able to:

Install and configure a Jenkins and Jira CICD and issue management environment using Docker containers
Configure Jenkins with the Gradle tool to perform the core build and packaging for a sample Java servlet web application
Configure Jenkins with the Jira Pipeline Steps plugin for automated issue management
Create and set up a Jenkins build pipeline using a Jenkinsfile stored within a GitHub repo
Kickoff a Jenkins build and review the build results
Use the Jira administration web console to manage the issues raised automatically by the Jenkins pipeline build

You should:

Be comfortable with SSH to remotely administer a Linux-based server
Be comfortable with basic Linux administration

Lab Environment

This lab will start with the following AWS resources being provisioned automatically for you:

A single EC2 instance, named cicd.platform.instance, which will have a public IP address attached

To achieve the lab end state, you will be walked through the process of:

SSHing into the EC2 instance, named cicd.platform.instance
- Use Docker Compose to launch the following Docker containers:
  - Jenkins
  - Jira
  - Socat
Using a browser, administer and configure Jenkins - installing the required plugins. Connectivity to Jenkins will be done via the cicd.platform.instance Public IP address
Using a browser, administer and configure Jira. Connectivity to Jira will be done via the cicd.platform.instance Public IP address
Create a Jenkins build pipeline and configure it to build a sample Java servlet web application hosted on GitHub
Execute the Jenkins build pipeline and confirm that it has completed successfully, registering a new Jira ticket automatically, and attaching the Gradle build log file
Use the Jira administration console to manage the ticket raised by the Jenkins pipeline build process