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)

Reverting changes

Sometimes, you just want to get rid of whatever it is you did. Whether you just want to clean your working directory or you want to actually undo some items you (accidentally) committed, Git makes it possible.

There are a couple of scenarios we can think of that we want reverted. The first is quite simple. We have staged some files and we simply want to unstage everything. The git reset command does this:

git status
On branch master
Changes to be committed:
(use "git reset HEAD <file>..." to unstage)

new file: accidentally added.txt
modified: kernel.txt
deleted: lasers.txt

git reset
Unstaged changes after reset:
M kernel.txt
D lasers.txt

git status
On branch master
Changes not staged for commit:
(use "git add/rm <file>..." to update what will be committed)
(use "git checkout -- <file>..." to discard changes in working directory...