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.
Table of Contents (15 chapters)
Learning Continuous Integration with Jenkins
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Continuous Delivery Design


The Continuous Delivery Design that we are going to discuss now is a simple extension of the Continuous Integration Design that we discussed in Chapter 4, Continuous Integration Using Jenkins – Part I. This includes creating new Jenkins jobs as well as modifying the already existing Jenkins jobs that are part of the Continuous Integration Design.

Continuous Delivery pipeline

Continuous Integration is an integral part of Continuous Delivery. Hence, all Jenkins jobs that were created as part of the Continuous Integration Design will fall into the Continuous Delivery Design by default. From the previous chapters, we are familiar with the following Continuous Integration pipelines:

  • The pipeline to poll the feature branch

  • The pipeline to poll the integration branch

However, as part of our CD Design, the pipeline to poll the integration branch will be modified by reconfiguring the existing Jenkins jobs and adding new Jenkins jobs. Together, these new Jenkins pipelines will...