Book Image

Learning Continuous Integration with Jenkins - Second Edition

By : Nikhil Pathania
Book Image

Learning Continuous Integration with Jenkins - Second Edition

By: Nikhil Pathania

Overview of this book

In past few years, agile software development has seen tremendous growth. There is a huge demand for software delivery solutions that are fast yet flexible to numerous amendments. As a result, Continuous Integration (CI) and Continuous Delivery (CD) methodologies are gaining popularity. This book starts off by explaining the concepts of CI and its significance in the Agile. Next, you'll learn how to configure and set up Jenkins in many different ways. The book exploits the concept of "pipeline as code" and various other features introduced in the Jenkins 2.x release to their full potential. We also talk in detail about the new Jenkins Blue Ocean interface and the features that help to quickly and easily create a CI pipeline. Then we dive into the various features offered by Jenkins one by one, exploiting them for CI and CD. Jenkins' core functionality and flexibility allows it to fit in a variety of environments and can help streamline the development process for all stakeholders. Next, you'll be introduced to CD and will learn how 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 CI and CD using Jenkins.
Table of Contents (18 chapters)
Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
Index

Distributed build and test


In the following section let us learn a little bit about the distributed build and testing. Imagine you have a really fat unit test or integration test suite. If you can divide them in small parts then you can run them in parallel. To run them in parallel you need multiple clones of your build/test machines. If you have them in place either using Docker or using some other mechanism, then the remaining thing to do is to make them a Jenkins slave agent.

The following illustration shows how a Jenkins pipeline to build, unit test and integration test utilizes the distributed build/test farm in Jenkins. You can see, we have two categories of Jenkins slave agents: Standalone Jenkins slave for build and unit test, and standalone Jenkins slave for integration test.

The unit testing is distributed across three Jenkins slave agents for build and unit test (category 1), and the integration testing is distributed across two Jenkins slave agents for integration testing (category...