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)

The basics

Before we head over to the more advanced stuff, let's go over the basics. You have already done most of this in the previous chapters, but getting a good grasp of what is going on is important if you want to use Git effectively and to the fullest. I recommend creating a new Git repository so you can experiment and throw out your repository when we are done.

Centralized Source Control Management

In traditional Source Control Management (SCM) systems, such as CVS and Subversion, which have long been the industry standards, your code was saved to a server. This server kept the entire history of your project. Developers working on the project could check out a snapshot of the project, make their changes, and commit...