Book Image

Continuous Integration, Delivery, and Deployment

By : Sander Rossel
Book Image

Continuous Integration, Delivery, and Deployment

By: Sander Rossel

Overview of this book

The challenge faced by many teams while implementing Continuous Deployment is that it requires the use of many tools and processes that all work together. Learning and implementing all these tools (correctly) takes a lot of time and effort, leading people to wonder whether it's really worth it. This book sets up a project to show you the different steps, processes, and tools in Continuous Deployment and the actual problems they solve. We start by introducing Continuous Integration (CI), deployment, and delivery as well as providing an overview of the tools used in CI. You'll then create a web app and see how Git can be used in a CI environment. Moving on, you'll explore unit testing using Jasmine and browser testing using Karma and Selenium for your app. You'll also find out how to automate tasks using Gulp and Jenkins. Next, you'll get acquainted with database integration for different platforms, such as MongoDB and PostgreSQL. Finally, you'll set up different Jenkins jobs to integrate with Node.js and C# projects, and Jenkins pipelines to make branching easier. By the end of the book, you'll have implemented Continuous Delivery and deployment from scratch.
Table of Contents (15 chapters)

Running on Windows with Jenkins Slaves

We have come pretty far in what we can do using Jenkins, all automated. However, there is still the issue that we are running on Ubuntu. We still need to test our code on Internet Explorer and Edge and, in the real world, probably Safari. Unfortunately, we are stuck on Ubuntu, or so it seems. Luckily, Jenkins has a neat feature that enables us to run Jenkins remotely on different computers, slaves, or nodes.

Go to your Jenkins management and find Manage Nodes. On the menu, click New Node. Pick a node name, for example, Windows Slave, and make it Permanent Agent (at this point you probably have no other choice). In the next form, choose a remote root directory, something like C:\Jenkins (this is going to run on Windows!). Also, give this node the windows label and choose Only build jobs with label expression matching this node for usage. Optionally...