Book Image

Learning Continuous Integration with Jenkins - Second Edition

By : Nikhil Pathania
Book Image

Learning Continuous Integration with Jenkins - Second Edition

By: Nikhil Pathania

Overview of this book

In past few years, agile software development has seen tremendous growth. There is a huge demand for software delivery solutions that are fast yet flexible to numerous amendments. As a result, Continuous Integration (CI) and Continuous Delivery (CD) methodologies are gaining popularity. This book starts off by explaining the concepts of CI and its significance in the Agile. Next, you'll learn how to configure and set up Jenkins in many different ways. The book exploits the concept of "pipeline as code" and various other features introduced in the Jenkins 2.x release to their full potential. We also talk in detail about the new Jenkins Blue Ocean interface and the features that help to quickly and easily create a CI pipeline. Then we dive into the various features offered by Jenkins one by one, exploiting them for CI and CD. Jenkins' core functionality and flexibility allows it to fit in a variety of environments and can help streamline the development process for all stakeholders. Next, you'll be introduced to CD and will learn how 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 CI and CD using Jenkins.
Table of Contents (18 chapters)
Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
Index

Installing and configuring Artifactory


Continuous integration results in frequent builds and packages. Hence, there is a need for a mechanism to store all this binary code (builds, packages, third-party plugins, and so on) in a system akin to a version control system.

Since version control systems such as Git, TFS, and SVN store code and not binary files, we need a binary repository tool. A binary repository tool such as Artifactory or Nexus tightly integrated with Jenkins provides the following advantages:

  • Tracking builds (who triggers? What code was built?)
  • Dependencies
  • Deployment history

The following diagram depicts how a binary repository tool such as Artifactory works with Jenkins to store build artifacts. In the coming topics, we will learn how to achieve this by creating a Jenkins job to upload code to Artifactory:

Jenkins pipeline pushing built artifacts to Artifactory

In the current book, we will be dealing with Artifactory to store our builds. Artifactory is a tool used to version control...