Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Practical DevOps, Second Edition

You're reading from   Practical DevOps, Second Edition Implement DevOps in your organization by effectively building, deploying, testing, and monitoring code

Arrow left icon
Product type Paperback
Published in May 2018
Publisher Packt
ISBN-13 9781788392570
Length 250 pages
Edition 2nd Edition
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
joakim verona joakim verona
Author Profile Icon joakim verona
joakim verona
Arrow right icon
View More author details
Toc

Table of Contents (12) Chapters Close

Preface 1. Introducing DevOps and Continuous Delivery FREE CHAPTER 2. A View from Orbit 3. How DevOps Affects Architecture 4. Everything is Code 5. Building the Code 6. Testing the Code 7. Deploying the Code 8. Monitoring the Code 9. Issue Tracking 10. The Internet of Things and DevOps 11. Other Books You May Enjoy

Why do we build code?

Most developers are familiar with the process of building code. When we work in the field of DevOps, however, we might face issues that developers who specialize in programming a particular component type won't necessarily experience.

For the purposes of this book, we define software building as the process of molding code from one form to another. During this process, several things might happen:

  • The compilation of source code to native code or virtual machine bytecode, depending on our production platform.
  • Linting of the code, which involves checking the code for errors and generating code quality measures by means of static code analysis. The term linting originated with a program called lint, which started shipping with early versions of the Unix operating system. The purpose of the program was to find bugs in programs that were syntactically correct...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime