chapter six

6 Deploying HA Jenkins on Multiple Cloud Providers

 

This chapter covers

  • Build process automation of Jenkins virtual machine images with Packer.
  • Deployment of Jenkins cluster on Microsoft Azure, Google Cloud Platform & DigitalOcean.
  • Reducing the cost of Jenkins workers deployment by creating them on-demand.
  • Usage of the same Packer template multiple times to create identical Jenkins machine images in different cloud providers.

We already saw how to accomplish fault tolerance by deploying Jenkins cluster in Amazon Web Services (AWS). The chapter will try to achieve the same required speed and automation on the infrastructure level by using the same tools and processes to automate the creation of a cluster on different cloud providers such as Microsoft Azure, Google Cloud Platform and DigitalOcean ranging from Infrastructure as a Service (IaaS) to Platform as a Service (PaaS) providers.

You might notice that some parts of this chapter are very similar, or even the same as those you read in the previous chapter. The reason for the partial repetition is to achieve the goal of this book which is to illustrate the usage of Jenkins with cloud native applications and because not everyone is adopting AWS as a main provider, we want to make this book useful for others and for those who skipped the AWS chapter and jumped right here.

6.1      Google Cloud Platform

6.1.1   Building Jenkins VM images

6.1.2   Configuring GCP Network with Terraform

6.1.3   Deploying Jenkins on Google Compute Engine

6.1.4   Launching auto-managed workers on GCP

6.2      Microsoft Azure

6.2.1   Building golden Jenkins VM images in Azure

6.2.2   Deploying private virtual network

6.2.3   Deploying Jenkins master virtual machine

6.2.4   Applying autoscaling to Jenkins workers

6.3      DigitalOcean

6.3.1   Creating Jenkins DigitalOcean Snapshots

6.3.2   Deploying Jenkins Master Droplet

6.3.3   Building Jenkins Workers Droplets

6.4      Summary