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

Best practices for Jenkins jobs


Using Distributed builds, version controlling the Jenkins configuration, implementing auditing of Jenkins and all the Jenkins configurations, features and plugins that we have seen in the current book were implemented in the best possible way. However, there are few critical things that were not discussed so far and need our attention. Let's see them one by one.

Avoiding scheduling all jobs to start at the same time

Multiple Jenkins jobs triggered at the same time may choke your Jenkins. To avoid this, avoid scheduling all jobs to start at the same time.

To produce even load on the system, use the symbol H. For example, using 0 0 * * * for a dozen daily jobs will cause a large bottleneck at midnight. Instead, using H H * * * would still execute each job once a day, but not all at the same time.

The H symbol can be used with a range. For example, H H(0-7) * * * means sometime between 12:00 A.M. (midnight) to 7:59 A.M. You can also use step intervals with H, with...