Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Continuous Integration, Delivery, and Deployment
  • Table Of Contents Toc
Continuous Integration, Delivery, and Deployment

Continuous Integration, Delivery, and Deployment

By : Rossel
4 (8)
close
close
Continuous Integration, Delivery, and Deployment

Continuous Integration, Delivery, and Deployment

4 (8)
By: 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)
close
close

Continuous Delivery

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...

Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Continuous Integration, Delivery, and Deployment
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist download Download options font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon