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.

Preface

What this book covers

What you need for this book

Who this book is for

Reader feedback

Customer support

Free Chapter

Continuous Integration, Delivery, and Deployment Foundations

Continuous Integration, Delivery, and Deployment Foundations

Continuous Integration

Continuous Delivery

Continuous Deployment

Setting Up a CI Environment

Setting Up a CI Environment

Installing a Virtual Machine

Installing Jenkins

Installing PostgreSQL

Installing SonarQube

Version Control with Git

Version Control with Git

Reverting changes

The branching model

Creating a Simple JavaScript App

Creating a Simple JavaScript App

The web shop specs

Installing Node.js and npm

Creating the project

Creating the Home page

Creating the Product page

Creating the Search page

Creating the Shopping cart page

Testing Your JavaScript

Testing Your JavaScript

Unit testing with Jasmine

Testing the web shop

Running tests with Karma

End-To-End testing with Selenium

Headless browser testing

Automation with Gulp

Automation with Gulp

Running your Karma tests

Getting our site production ready

Putting it all together

Automation with Jenkins

Automation with Jenkins

Installing Node.js and npm

Creating a Jenkins project

Executing Gulp in Jenkins

Publishing test results

Setting up email notifications

Setting up SonarQube

Running on Windows with Jenkins Slaves

A NodeJS and MongoDB Web App

A NodeJS and MongoDB Web App

Installing MongoDB

Creating the Node.js Back-end

Saving to MongoDB

Moving the Shopping Cart Module

A C# .NET Core and PostgreSQL Web App

A C# .NET Core and PostgreSQL Web App

Installing .NET Core and Visual Studio Code

Creating the views

Adding the database

Fixing the login

Testing the database

Testing our C# code

Adding Selenium tests

Additional Jenkins Plugins

Additional Jenkins Plugins

Cleanup workspaces

Conditional build steps

Promoted builds

Parameterized builds

Triggering builds remotely

Jenkins Pipelines

Jenkins Pipelines

Pipeline projects

The Jenkinsfile

Multibranch pipeline

Completing the script

Testing a Web API

Testing a Web API

Building a REST service

Continuous Delivery

Continuous Delivery

Manual deployment

Continuous Deployment

Continuous Deployment

JavaScript Deployment using SSH

C# .NET Core Deployment using SSH

Customer Reviews

5 star

0

4 star

0

3 star

0

2 star

0

1 star

0

JavaScript Deployment using SSH

The first thing we need to do is get out artifacts from our Jenkins build to where we want them fully automated. Usually, this will be some remote server, but we do not have that. However, what we will do is to pretend that our local Linux machine is some other remote Linux machine and transfer the files using SSH.

First, in our master Jenkinsfile, we will need to unpack our artifacts so that we can copy them at all. Jenkins will mention that unarchive is deprecated and replaced for most purposes by stash and unstash. As far as I know, stash and unstash are temporary for the duration of the build, while archive keeps your artifacts even when the build is complete. We need the archive because we always want to know what is currently running on production and maybe because we want to be able to manually deploy files as well. The only way to get your...