Book Image

Learning Continuous Integration with Jenkins

By : Nikhil Pathania
Book Image

Learning Continuous Integration with Jenkins

By: Nikhil Pathania

Overview of this book

In past few years, Agile software development has seen tremendous growth across the world. There is huge demand for software delivery solutions that are fast yet flexible to frequent amendments. As a result, CI and continuous delivery methodologies are gaining popularity. Jenkins’ core functionality and flexibility allows it to fit in a variety of environments and can help streamline the development process for all stakeholders. This book starts off by explaining the concepts of CI and its significance in the Agile world with a whole chapter dedicated to it. Next, you’ll learn to configure and set up Jenkins. You’ll gain a foothold in implementing CI and continuous delivery methods. We dive into the various features offered by Jenkins one by one exploiting them for CI. After that, you’ll find out how to use the built-in pipeline feature of Jenkins. You’ll see how to integrate Jenkins with code analysis tools and test automation tools in order to achieve continuous delivery. Next, you’ll be introduced to continuous deployment and learn to achieve it using Jenkins. Through this book’s wealth of best practices and real-world tips, you'll discover how easy it is to implement a CI service with Jenkins.

Related Content you might be interested in

Current Title:

Small book image
Learning Continuous Integration with Jenkins
Nikhil Pathania
May, 2016 | 542 pages
No titles found
Table of Contents (15 chapters)
Learning Continuous Integration with Jenkins
Learning Continuous Integration with Jenkins
Credits
Credits
About the Author
About the Author
About the Reviewer
About the Reviewer
www.PacktPub.com
www.PacktPub.com
Preface
Preface
Free Chapter
1
Concepts of Continuous Integration
Concepts of Continuous Integration
The agile software development process
Continuous Integration
The best practices of Continuous Integration
How to achieve Continuous Integration
Continuous Integration benefits
Summary
2
Setting up Jenkins
Setting up Jenkins
Introduction to Jenkins
Running Jenkins inside a container
Running Jenkins as a standalone application
Sample use cases
Summary
3
Configuring Jenkins
Configuring Jenkins
Creating your first Jenkins job
Jenkins backup and restore
Upgrading Jenkins
Managing Jenkins plugins
User administration
Summary
4
Continuous Integration Using Jenkins – Part I
Continuous Integration Using Jenkins – Part I
Jenkins Continuous Integration Design
Setting up a version control system
Configuring Jenkins
The Jenkins pipeline to poll the feature branch
Summary
5
Continuous Integration Using Jenkins – Part II
Continuous Integration Using Jenkins – Part II
Installing SonarQube to check code quality
Installing Artifactory
Jenkins configuration
The Jenkins pipeline to poll the integration branch
Creating a nice visual flow for the Continuous Integration pipeline
Continuous Integration in action
Summary
6
Continuous Delivery Using Jenkins
Continuous Delivery Using Jenkins
What is Continuous Delivery?
Continuous Delivery Design
Configuring our testing server
Jenkins configuration
Creating Jenkins Continuous Delivery pipeline
Creating a nice visual flow for the Continuous Delivery pipeline
Creating a simple user acceptance test using Selenium and TestNG
Continuous Delivery in action
Summary
7
Continuous Deployment Using Jenkins
Continuous Deployment Using Jenkins
What is Continuous Deployment?
Continuous Deployment Design
Configuring the production server
Jenkins configuration
Creating the Jenkins Continuous Deployment pipeline
Creating a nice visual flow for the Continuous Delivery pipeline
Continuous Deployment in action
Summary
8
Jenkins Best Practices
Jenkins Best Practices
Distributed builds using Jenkins
Version control Jenkins configuration
Auditing in Jenkins
Notifications
Best practices for Jenkins jobs
Summary
Index
Index

Installing Artifactory

Continuous Integration results in frequent builds and packages. Hence, there is a need for a mechanism to store all this binary code (builds, packages, third-party plugins, and so on) in a system akin to a version control system.

Since, version control systems such as Git, TFS, and SVN store code and not binary files, we need a binary repository tool. A binary repository tool such as Artifactory or Nexus that is tightly integrated with Jenkins provides the following advantages:

  • Tracking builds (Who triggers a build? What version of code in the VCS was build?)

  • Dependencies

  • Deployment history

The following image depicts how a binary repository tool such as Artifactory works with Jenkins to store build artifacts. In the coming sections, we will see how to achieve this by creating a Jenkins job to upload code to Artifactory.

In this book, we will use Artifactory to store our builds. Artifactory is a tool used to version control binaries. The binaries can be anything from built...

Previous Section
End of Section 3
Next Section