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

Architecting a build pipeline


Build pipelines are the progression of logical development, quality and delivery steps; these steps define the way a software project will be built, delivered, and tested. By implementing build pipelines, we are crafting a solution where build packages or containers flow through repeatable delivery processes in a continuous manner. Gates are added to the pipeline to ensure that quality metrics are collected, and integration defects are identified. Each gate defined in the pipeline represents a go/no-go determination. Eventually, the automation solution vets and releases a build through the complete pipeline and into a production or released status.

As we hinted earlier, production does not always need to apply to cloud-based software or rack-mounted servers. The production or released status of a build pipeline simply represents the end goal. For embedded solutions or shrink-wrapped software, build pipelines can still provide high levels of value, and can further...