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)

Branching

We have discussed branching using Git in Chapter 3, Version Control with Git. We have discussed how your code should go from a commit on a development environment to a test environment, be it automatically tested and manually tested if necessary; then an acceptance environment where the customer can have a look at it and finally, a production environment where customers can use the software pretty much fully automated. So, you will have to set up a complete DTAP street (Development, Test, Acceptance, and Production), but still be able to differentiate between them all.

Perhaps you may have more or fewer environments, but you still want to know what commits are on what environment. We are going to set up one of those environments in this chapter. First, we are going to look at the process of branching your software so it can be distributed to the different (fictional...