Book Image

Mastering Jenkins

By : jmcallister -, Jonathan McAllister
Book Image

Mastering Jenkins

By: jmcallister -, Jonathan McAllister

Overview of this book

With the software industry becoming more and more competitive, organizations are now integrating delivery automation and automated quality assurance practices into their business model. Jenkins represents a complete automation orchestration system, and can help converge once segregated groups into a cohesive product development and delivery team. By mastering the Jenkins platform and learning to architect and implement Continuous Integration, Continuous Delivery, and Continuous Deployment solutions, your organization can learn to outmanoeuvre and outpace the competition. This book will equip you with the best practices to implement advanced continuous delivery and deployment systems in Jenkins. The book begins with giving you high-level architectural fundamentals surrounding Jenkins and Continuous Integration. You will cover the different installation scenarios for Jenkins, and see how to install it as a service, as well as the advanced XML configurations. Then, you will proceed to learn more about the architecture and implementation of the Jenkins Master/Save node system, followed by creating and managing Jenkins build jobs effectively. Furthermore, you'll explore Jenkins as an automation orchestration system, followed by implementing advanced automated testing techniques. The final chapters describe in depth the common integrations to Jenkins from third-party tools such as Jira, Artifactory, Amazon EC2, and getting the most out of the Jenkins REST-based API. By the end of this book, you will have all the knowledge necessary to be the definitive resource for managing and implementing advanced Jenkins automation solutions for your organization.
Table of Contents (18 chapters)
Mastering Jenkins
Credits
Foreword
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

The value proposition of build pipelines


For software organizations, defects can be extremely costly. For each defect identified, the amount of time spent by engineering, quality assurance, and related teams to rectify it is equivalent to the amount of time and resources that are distracted from feature development and strategic business initiatives. It is, by nature, a one to one ratio. Identifying and addressing defects earlier in the software development lifecycle by through the use of build pipelines can save multitudes of time, resources and solidify business credibility.

Over the years, there have been a number of independent research studies conducted to better quantify the relative costs associated with software development efforts including bug fixing, software architecture, project management, and so on. The most notable research into defect analysis, specifically, was conducted by Barry Boehm in 2007 and is illustrated in Figure 7-1.

Figure 7-1: Relative cost of bug fixes

His research...