Book Image

Practical DevOps - Second Edition

By : joakim verona
Book Image

Practical DevOps - Second Edition

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 code workflows from testing environments to production environments. It stresses cooperation between different roles, and how they can work together more closely, as the roots of the word imply—Development and Operations. Practical DevOps begins with a quick refresher on DevOps and continuous delivery and quickly moves on to show you how DevOps affects software architectures. You'll create a sample enterprise Java application that you’'ll continue to work with through the remaining chapters. Following this, you will explore various code storage and build server options. You will then learn how to test your code with a few tools and deploy your test successfully. In addition to this, you will also see how to monitor code for any anomalies and make sure that it runs as expected. Finally, you will discover how to handle logs and keep track of the issues that affect different processes. By the end of the book, you will be familiar with all the tools needed to deploy, integrate, and deliver efficiently with DevOps.
Table of Contents (12 chapters)

Building the Code

You need a system to build your code, and you need somewhere to build it.

This chapter discusses build systems, systems that convert source code into various types of artifacts, and systems that check code validity, among other things. The chapter will cover the following topics:

  • Why do we build code? Here, we discuss the purpose of building code.
  • The many faces of build systems. Here, we will explore the different build systems and how they affect our DevOps work.
  • The Jenkins build server. Jenkins is a flexible open source build server that grows with your needs. Some alternatives to Jenkins will be explored as well.
  • Managing build dependencies. You need many bits and pieces to compile code into usable artifacts. These are called build dependencies
  • Collating quality measures. Here, we discuss ways of measuring code quality
  • Taking build errors seriously. Here...