concept vcs in category legacy software

appears as: VCS
Re-Engineering Legacy Software

This is an excerpt from Manning's book Re-Engineering Legacy Software.

There’s a simple solution to this. Instead of configuring Jenkins to poll, set up the VCS to tell Jenkins about changes as soon as they occur. This can be done by configuring a hook in your VCS system. The details depend on the particular VCS implementation that you’re using, but most modern VCS solutions have support for Webhooks or something similar.

4.1.4. Lean on the VCS

I assume that you’re using a version control system (VCS) such as Git, Mercurial, or SVN to manage your source code. (If not, put this book down and go and fix that situation right now!) This can be really useful when refactoring. If you get into the habit of committing regularly, you can treat the VCS as a giant Undo button. Any time you feel like your refactoring is getting out of control, you have the freedom to back out by hitting the Undo button (reverting to the previous commit).

Refactoring is often an exploratory experience in which you don’t know whether a particular solution will work out until you try it. The safety net of the VCS gives you the freedom to experiment with a number of solutions, safe in the knowledge that you can back out whenever you want. In fact, effective use of branches means that you can have a few different solutions on the go at the same time, while you explore the pros and cons of each approach.