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

Summary


We began the chapter by discussing a Continuous Integration Design that contained a branching strategy, some tools for CI, and a CI Pipeline structure. We also saw how to install and configure Git along with the plugin that connects it with Jenkins.

The CI pipeline structure discussed as part of the CI design contained two pipelines: one for polling the feature branch and another one for polling the integration branch. Creating the pipeline to poll the feature branch was what we did in the second half of the chapter. This involved polling the feature branch for changes, performing a Maven build, unit testing, and publishing Javadoc. Later, we saw how to merge the successfully built and tested code into the integration branch.

However, this was half the story. The next chapter is all about creating the Jenkins pipeline to poll the Integration branch, wherein we will see how the successfully merged code on the integration branch is built and tested for integration issues and lots more...