Book Image

The DevOps Career Handbook

By : John Knight, Nate Swenson
Book Image

The DevOps Career Handbook

By: John Knight, Nate Swenson

Overview of this book

DevOps is a set of practices that make up a culture, and practicing DevOps methods can make developers more productive and easier to work with. The DevOps Career Handbook is filled with hundreds of tips and tricks from experts regarding every step of the interview process, helping you save time and money by steering clear of avoidable mistakes. You’ll learn about the various career paths available in the field of DevOps, before acquiring the essential skills needed to begin working as a DevOps professional. If you are already a DevOps engineer, this book will help you to gain advanced skills to become a DevOps specialist. After getting to grips with the basics, you'll discover tips and tricks for preparing your resume and online profiles and find out how to build long-lasting relationships with the recruiters. Finally, you'll read through interviews which will give you an insight into a career in DevOps from the viewpoint of individuals at different career levels. By the end of this DevOps book, you’ll gain a solid understanding of what DevOps is, the various DevOps career paths, and how to prepare for your interview.
Table of Contents (17 chapters)
1
Section 1: A Career in DevOps
5
Section 2: The Application Process
10
Section 3: Interview Process
13
Section 4: Tips, Tricks, and Interviews

CI/CD concepts

Continuous Integration (CI) and Continuous Delivery (CD) are synonymous with DevOps. This is because every practice discussed in Chapter 1, Career Paths – plan, code, build, test, release, deploy, and operate – is included in the infinite CI/CD loop, as shown in Figure 2.16:

Figure 2.16 – Infinite CI/CD loop

Let's first examine CI and the related practices and tools associated with it.

Continuous integration

Continuous integration is the process of merging code changes from multiple developers into a single branch on a regular and frequent basis. To do this effectively, you need some form of automation that builds your code and executes a battery of tests against it. CI servers help to effectively integrate your code using CI pipelines.

After a developer makes a change, code changes are committed to a source code management system by using git. The CI server has a built-in listener (hook) to trigger a build...