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)

A C# .NET Core and PostgreSQL Web App

In the previous chapter, we completed our web shop example. After the frontend we created, built, and tested in the previous chapters, we added the backend and adjusted our tests. All we used so far was JavaScript. However, languages, such as Java and C#, require other methods of testing and building. Some of the major differences here are that these are typed and compiled languages. In this chapter, we are going to set up the website again but this time, using C#. As a backend, we will use PostgreSQL, a popular SQL database. Along the way we will see how building and testing differs from that of JavaScript and how the Visual Studio environment tooling helps us to do the things we need.

To build our C# website, we are going to use Visual Studio Code, the little brother of Microsoft's flagship IDE Visual Studio. Unlike Visual Studio, Visual...