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)

Completing the script

So far, we know how to utilize the multibranch pipeline and we have most of a working script, but it is not completely what we configured earlier in classic Jenkins. So, let's complete the script so we have pretty much everything. We can now also easily differentiate between different branches. Basically, I want to get everything up and running as though we were building an actual product. We will fill in the final details on releasing the software in the final chapters of this book.

First, we are going to make a few edits to our gulpfile. It was fine earlier, but now that we are going to trigger three builds at the same time, it makes no sense to use PhantomJS every time. Also, we want to be able to trigger the test-min task without also triggering the regular test task. The change is pretty simple. Just change the browsers Karma configuration in the...