Jenkins Essentials - Second Edition

Jenkins Essentials - Second Edition

By : Mitesh Soni

Buy this Book

Jenkins Essentials - Second Edition

By: Mitesh Soni

Buy this Book

Overview of this book

In agile development practices, developers need to integrate their work frequently to fix bugs or to create a new feature or functionality. Jenkins is used specifically for Continuous Integration, helping to enforce the principles of agile development. This book focuses on the latest and stable release of Jenkins (2.5 and later), featuring the latest features, such as Pipeline as Code, the new setup experience, and the improved UI. With the all-new Pipeline as Code feature, you will be able to build simple or advanced pipelines easily and rapidly, hence improving your teams' productivity. This book begins by tackling the installation of the necessary software dependencies and libraries you'll need to perform Continuous Integration for a Java application. From there, you'll integrate code repositories, applications, and build tools for the implementation of Continuous Integration. Finally, you will also learn how to automate your deployment on cloud platforms such as AWS and Microsoft Azure, along with a few advanced testing techniques.

Title Page

Credits

About the Author

About the Reviewers

www.PacktPub.com

Customer Feedback

Dedication

Preface

Free Chapter

Exploring Jenkins

Introduction of Jenkins 2

Installation of Jenkins 2

Jumpstart tour of the Jenkins dashboard

Configuration settings in Jenkins

Overview of the CI/CD pipeline

Summary

Installation and Configuration of Code Repository and Build Tools

Overview of Jenkins

Installing Java and configuring the environment variables

Installing and configuring Ant

Installing Maven

Configuring Ant, Maven, and JDK in Jenkins

First job in Jenkins

Installing and configuring the Git repository on CentOS

Eclipse and Jenkins integration

Summary

Managing Code Quality and Notifications

Jenkins 2.x integration with Sonar 6.3

Quality Gate plugin

Email notifications on build status

Summary

Continuous Integration with Jenkins

Dashboard View plugin

Creating and configuring a build job for a Java application with Ant

Creating and configuring a build job for a Java application with Maven

Summary

Continuous Delivery - Implementing Automated Deployment

An overview of Continuous Delivery and Continuous Deployment

Installing Tomcat

Deploying a war file from Jenkins to Tomcat

Deploying a WAR file from Jenkins to AWS Elastic Beanstalk

Deploying a war file from Jenkins to Microsoft Azure App Services

Summary

Continuous Testing - Functional and Load Testing with Jenkins

Functional testing with Selenium

Load testing with Apache JMeter

Summary

Build Pipeline and Pipeline as a Code

Build Pipeline

Overview of pipeline as a code

Promoted builds

Summary

Managing and Monitoring Jenkins

Managing Jenkins master and slave nodes

Monitoring Jenkins with JavaMelody

Managing job-specific configurations - backup and restore

Managing disk usage

Build job-specific monitoring with the Build Monitor plugin

Audit Trail plugin-overview and usage

Workspace Cleanup plugin

Conditional Build Step plugin

EnvInject plugin

Summary

Security in Jenkins

User management

Role-based security

Project-based security

Summary

Customer Reviews

5 star

4 star

3 star

2 star

1 star

Installation of Jenkins 2

Let's start with Jenkins 2.x installation. Go to https://jenkins.io/ and click on the Download button to download packages for installation of Jenkins:

At https://jenkins.io/download/, we get two sections. One is for Long-term Support (LTS) that is selected after every 12 weeks from regular releases as the stable release from that duration.

Another section is Weekly release, which has bug fixes and is made available to users and developers.

We will use the Generic Java Package (.war) file in our installation of Jenkins as shown in the following screenshot.

The reason for selecting the .war file for the Jenkins installation is its ease of use across operating systems. Jenkins is written in Java, and in any case, to execute Jenkins we need the latest Java version installed on our system. For Jenkins Installation, Java 8 is recommended. It is recommended to have 1-GB of memory.

Verify the Java installation by using the java -version command in the command prompt or terminal based on the operating system.

Download Generic Java Package (.war) from https://jenkins.io/download/ on the local system as follows:

Before we start Jenkins, we will set the JENKINS_HOME environment variable. When we install and configure Jenkins, all the files reside in the jenkins directory by default. We often need to change the default location for our convenience. We can do that by setting the JENKINS_HOME environment variable. Follow the following steps:

To set the JENKINS_HOME environment variable in Windows 10, go to Control Panel | All Control Panel Items | System and click on Advanced system settings | Advanced | Environment Variables... Please see the manual for other operating systems to set Environment Variables...:

Click on New. Enter the variable name and location and click OK:

Now our JENKINS_HOME is set so Jenkins will use that directory to store all configuration files.
Open the command prompt or terminal (depending on your operating system) and execute the following command:

Java -jar Jenkins.war

This is a fresh installation of Jenkins, so initial setup is required. Note the password:

Once Jenkins is fully up and running, visit http://localhost:8080 and it will open the Getting Started page to Unlock Jenkins. Give the password we copied from the terminal or go to the location given in the dialog box. Copy the password from there and click on Continue:

Click on Install to see the suggested plugins. If we are behind the proxy, then another dialog box will pop up before this page to provide proxy details: