Book Image

Practical DevOps

By : joakim verona
Book Image

Practical DevOps

By: joakim verona

Overview of this book

DevOps is a practical field that focuses on delivering business value as efficiently as possible. DevOps encompasses all the flows from code through testing environments to production environments. It stresses the cooperation between different roles, and how they can work together more closely, as the roots of the word imply—Development and Operations. After a quick refresher to DevOps and continuous delivery, we quickly move on to looking at how DevOps affects architecture. You'll create a sample enterprise Java application that you’ll continue to work with through the remaining chapters. Following this, we explore various code storage and build server options. You will then learn how to perform code testing with a few tools and deploy your test successfully. Next, you will learn how to monitor code for any anomalies and make sure it’s running properly. Finally, you will discover how to handle logs and keep track of the issues that affect processes
Table of Contents (17 chapters)
Practical DevOps
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

The history of source code management


In order to understand the central need for source code control, it can be illuminating to have a brief look at the development history of source code management. This gives us an insight into the features that we ourselves might need. Some examples are as follows:

  • Storing historical versions of source in separate archives.

    This is the simplest form, and it still lives on to some degree, with many free software projects offering tar archives of older releases to download.

  • Centralized source code management with check in and check out.

    In some systems, a developer can lock files for exclusive use. Every file is managed separately. Tools like this include RCS and SCCS.

    Note

    Normally, you don't encounter this class of tool anymore, except the occasional file header indicating that a file was once managed by RCS.

  • A centralized store where you merge before you commit. Examples include Concurrent Versions System (CVS) and Subversion.

    Subversion in particular is still...