Book Image

Mastering Jenkins

By : jmcallister -, McAllister
Book Image

Mastering Jenkins

By: jmcallister -, 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 (12 chapters)
11
Index

The Software Development Lifecycle


The Software Development Lifecycle (SDLC) can be described as the unique phases a software project journeys through from birth to release. A traditional SDLC includes planning, engineering, and test and release phases. These phases are designed to be circular in nature and future iterations of the project will inherently repeat the previously taken SDLC steps. Figure 5-5 illustrates a traditional SDLC:

Figure 5-5: The Software Development Lifecycle

The model described earlier illustrates a traditional waterfall approach to software development. In a continuous delivery or continuous deployment model, the iterations are much smaller, and an automated pipeline will need to be carefully created to support the higher velocity of releases in conjunction with dynamic automated testing.

To support the above stated modern continuous practices the SDLC will need to be expanded to reflect the shift towards continuous integration, continuous delivery, and continuous...