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 your Karma tests

Next, we want to run our tests. Of course, we already created some tests and ran them with Karma. No worries, we are not going to undo all that. Instead, we are going to run Karma automatically using Gulp. That way, we lint, test, and minify our code with a single gulp command. There used to be a Karma plugin for Gulp, but now it is recommended to just run Karma directly from Gulp. This is actually surprisingly easy:

var gulp = require('gulp');
var karma = require('karma').Server;

gulp.task('test', function () {
new karma({
configFile: __dirname + '/test/karma.conf.js'
}).start();
});

The __dirname variable is a global Node.js variable and contains the current file path. So, we set up a new Karma server from code, pass it our config file, and start it up. The config file still has PhantomJS set up and watches...