Book Image

Learning DevOps - Second Edition

By : Mikael Krief
Book Image

Learning DevOps - Second Edition

By: Mikael Krief

Overview of this book

In the implementation of DevOps processes, the choice of tools is crucial to the sustainability of projects and collaboration between developers and ops. This book presents the different patterns and tools for provisioning and configuring an infrastructure in the cloud, covering mostly open source tools with a large community contribution, such as Terraform, Ansible, and Packer, which are assets for automation. This DevOps book will show you how to containerize your applications with Docker and Kubernetes and walk you through the construction of DevOps pipelines in Jenkins as well as Azure pipelines before covering the tools and importance of testing. You'll find a complete chapter on DevOps practices and tooling for open source projects before getting to grips with security integration in DevOps using Inspec, Hashicorp Vault, and Azure Secure DevOps kit. You'll also learn about the reduction of downtime with blue-green deployment and feature flags techniques before finally covering common DevOps best practices for all your projects. By the end of this book, you'll have built a solid foundation in DevOps and developed the skills necessary to enhance a traditional software delivery process using modern software delivery tools and techniques.
Table of Contents (25 chapters)
1
Section 1: DevOps and Infrastructure as Code
7
Section 2: DevOps CI/CD Pipeline
11
Section 3: Containerized Microservices with Docker and Kubernetes
14
Section 4: Testing Your Application
18
Section 5: Taking DevOps Further/More on DevOps

Chapter 12: Static Code Analysis with SonarQube

In the previous chapter, we looked at how to test the functionality of an application programming interface (API) with Postman, a free tool for testing APIs, and the integration and automation of these tests in a continuous integration/continuous deployment (CI/CD) pipeline using Newman.

Testing the functionality of an API or application is a good practice when we wish to improve the quality of applications. In a company, the quality of an application must be considered by all its members because an application that brings business value to users increases the company's profits.

However, we often neglect to test the quality of an application's code because we think that what matters is how the application works and not how it is coded. This way of thinking is a big mistake because poorly written code can contain security vulnerabilities and can also cause performance problems. Moreover, the quality of the code has an impact...