We are finally getting into the next portion of this book, Continuous Delivery and Deployment. But, before we continue, let's have a brief recap of what we have learned so far. When we start working on a new project, the first thing we need is some source control repository. In this book, we have used Git. Using Git, we can create multiple branches to keep different environments and features apart. In this chapter, we are going to see why this is so important. While we write the software, we want to create automated tests, such as unit tests, E2E tests, and database tests. The more useful tests you have, the more reliable your software becomes. Upon each Git commit, we want to automatically test our software using continuous integration software, in our case, Jenkins. When our tests and, optionally, static code analyzers such as JSLint and SonarQube pass...
Continuous Integration, Delivery, and Deployment
By :
Continuous Integration, Delivery, and Deployment
By:
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.
Related Content you might be interested in
Current Title:
Continuous Integration, Delivery, and Deployment
Table of Contents (15 chapters)
Preface
Free Chapter
Continuous Integration, Delivery, and Deployment Foundations
Setting Up a CI Environment
Version Control with Git
Creating a Simple JavaScript App
Testing Your JavaScript
Automation with Gulp
Automation with Jenkins
A NodeJS and MongoDB Web App
A C# .NET Core and PostgreSQL Web App
Additional Jenkins Plugins
Jenkins Pipelines
Testing a Web API
Continuous Delivery
Continuous Deployment
Customer Reviews