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)

Putting it all together

By now, you are probably wondering if it is all worth it. There is just so much to do, with so many plugins and so many tasks and dependencies. Well, fear not. We can combine a lot of tasks in one task to make it easier.

We are going to do all of our JavaScript-related tasks in a single task. We now have the tasks lint, browserify, minify-js, test, and test-min. Unfortunately, the lint and test steps need to remain separate, but we can Browserify and minify in the same step. To run additional plugins after Browserify, we need to buffer the vinyl streams using the vinyl-buffer module:

npm install vinyl-buffer --save-dev

After that, we can just pipe browserify, source, buffer, size, minify, and dest in a single task:

return browserify({
entries: [file],
debug: true
})
.bundle()
.pipe(source(file))
.pipe(buffer())
.pipe(rename({
extname...