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

Running Jenkins on Docker


The true advantage of having Jenkins on Docker is when you have to quickly create multiple development and staging instances of your production Jenkins server. It's also very useful in redirecting the traffic to a secondary Jenkins server while you perform maintenance activities on the primary Jenkins server. While we will see these use cases later, let's first try to run Jenkins on Docker.

Prerequisites

Before we begin, make sure you have the following things ready:

  • We need a machine with at least 4 GB of RAM (the more the better) and a Multi-core processor.
  • Depending on how you manage the infrastructure in your team, the machine could be an instance on a cloud platform (such as AWS, DigitalOcean, or any other cloud platform), a bare metal machine, or it could be a VM (on VMware vSphere or any other server virtualization software).
  • The machines should have Ubuntu 16.04 or greater installed on it.
  • Check for admin privileges; the installation might ask for an admin username...