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

Connecting product codes to tests


When in grade school we all learned the concepts surrounding the scientific method. It involved formulating a hypothesis, and validating our hypothesis by gathering supporting proof. As a software project matures, learning to apply the scientific method to automated testing will become increasingly important. The implementation of these principles is actually quite simple. The code change or feature represents the hypothesis and the validation of the hypothesis is the test(s) written, which prove it. In a standard Test Driven Development (TDD) model, tests are written prior to the code change. This is a very powerful model with very visible benefits. As powerful as TDD is it's import to mention that strict enforcement of writing tests prior to implementation can lead to arbitrary restrictions in prototyping, and may not work effectively in all cases. The important thing to adhere to is simply a consistent incremental approach to writing tests for each change...