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)

Installing Node.js and npm

First things first, for our build, we need Node.js and npm (again) at the very least. Like on Windows, we can install Node.js and get npm as a bonus. We must install them on our CI server. Unlike Jenkins, Node.js has an install package in apt-get. Unfortunately, this is an old version and we want to use the latest LTS version. So again, we are going to run some arcane Linux commands:

curl -sL https://deb.nodesource.com/setup_6.x | sudo -E bash -
sudo apt-get install -y nodejs

The L switch (from -L) in curl tells it to redo the request if the response returns that the requested page has moved. We know the pipe character; it gives the output of the left side of the pipe's input to the right side of the pipe. sudo -E bash - will run the bash command as the root user (super user). -E means that any environment variables will be kept. The last - means...