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)

C# .NET Core Deployment using SSH

Next up is the C# web application. We have already done most of the work; now set up SSH.

Fixing our Jenkinsfile so that it copies our archived files automatically should not be a problem. We can do this again using SSH. First, we need to make Jenkins the owner of the webshop-net folder:

sudo chown -R jenkins:jenkins /var/www/webshop-net

Again, this means that your root user loses privileges, and if you want to copy using WinSCP, you should use the jenkins user.

After that, it is pretty much the same as for the JavaScript webshop:

sh 'rm -rf /var/www/webshop-net/*'
sh 'scp -r prod/* jenkins@ciserver:/var/www/webshop-net'

The complete code for the Archive Artifacts and Deployment steps looks as follows:

stage('Archiving Artifacts') {
steps {
node(label: 'linux') {
ws(dir: env.ws) {
sh &apos...