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)

Conditional build steps

Another useful Jenkins plugin is the Conditional BuildStep plugin (https://wiki.jenkins-ci.org/display/JENKINS/Conditional+BuildStep+Plugin). This plugin lets you skip or include build steps based on some condition. For example, you can build and unit test your source on every commit, but only run Selenium tests every three hours using a periodic build trigger (so your build is being tested even though there are no commits).

Install the Conditional BuildStep plugin in the plugin manager. After installation, you get two new build steps: Conditional step (single) and Conditional steps (multiple):

There are quite a few conditions to choose from. The Build Cause determines how the build was triggered (manual, SCM, or timer...), but you can also specify a day of the week, a time of the day, combine conditions with logical AND and OR clauses, and much more....