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)

Parameterized builds

It is possible to parameterize your builds in Jenkins. Create a new job and name it Parameterized Project or whatever. Now, almost at the top of the configuration is an option This project is parameterized. Check it and add a parameter. There are a couple of parameters and some plugins will add additional parameters. Most of them are pretty straightforward and all of them are explained in the help text. Let's go with a string parameter for simplicity. Pick a single word name, such as YourText, an optional default value, and an optional description:

Let your build run on Linux and add a shell script build step. That is where we can use any parameters:

echo $YourText

If you go back to the project page, you will notice that the Build button changed to Build with Parameters. If you try to run the build, you will be prompted with the parameters that you have...