Book Image

Learning DevOps

By : Mikael Krief
Book Image

Learning DevOps

By: Mikael Krief

Overview of this book

The implementation of DevOps processes requires the efficient use of various tools, and the choice of these tools is crucial for the sustainability of projects and collaboration between development (Dev) and operations (Ops). This book presents the different patterns and tools that you can use to provision and configure an infrastructure in the cloud. You'll begin by understanding DevOps culture, the application of DevOps in cloud infrastructure, provisioning with Terraform, configuration with Ansible, and image building with Packer. You'll then be taken through source code versioning with Git and the construction of a DevOps CI/CD pipeline using Jenkins, GitLab CI, and Azure Pipelines. This DevOps handbook will also guide you in containerizing and deploying your applications with Docker and Kubernetes. You'll learn how to reduce deployment downtime with blue-green deployment and the feature flags technique, and study DevOps practices for open source projects. Finally, you'll grasp some best practices for reducing the overall application lead time to ensure faster time to market. 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 (23 chapters)
Free Chapter
1
Section 1: DevOps and Infrastructure as Code
6
Section 2: DevOps CI/CD Pipeline
9
Section 3: Containerized Applications with Docker and Kubernetes
12
Section 4: Testing Your Application
16
Section 5: Taking DevOps Further

Using Travis CI for continuous integration

When we have an open source project, it is important to set up a continuous integration pipeline that has two roles:

  • To check the code changes that were proposed during a pull request that was opened by a contributor to the project. This verification will allow the code to be compiled and the unit tests from the pull request to be performed. The advantage of using this continuous integration process is that it blocks a pull request even before it has been opened and taken into account by other reviewers.
  • Compile the code and execute the unit tests present in the main branch and publish the binaries of the compilation result. These binaries can be published publicly either in a GitHub release, as we saw in the previous section, Sharing binaries in a GitHub release, in a package manager such as NuGet or npm, or in any other public marketplace...