- A pipeline is a sequence of automated operations that usually represents a part of the software delivery and quality assurance process.
- Step is a single automated operation, while stage is a logical grouping of steps used to visualize the Jenkins pipeline process.
- The
post
section defines a series of one or more step instructions that are run at the end of the pipeline build. - Checkout, Compile, and Unit test.
- Jenkinsfile is a file with the Jenkins pipeline definition (usually stored together with the source code in the repository).
- The code coverage stage is responsible for checking whether the source code is well covered with (unit) tests.
- An External trigger is a call from an external repository (such as GitHub) to the Jenkins master, while Polling SCM is a periodic call from the Jenkins master to the external repository.
- Email, Group Chat, Build Radiators, SMS, RSS Feed.
- Trunk-based workflow, Branching workflow, and Forking workflow.
- A feature toggle is a technique that is used to disable the feature for users, but enable it for developers while testing. Feature toggles are essentially variables used in conditional statements.
Continuous Delivery with Docker and Jenkins - Second Edition
By :
Continuous Delivery with Docker and Jenkins - Second Edition
By:
Overview of this book
Continuous Delivery with Docker and Jenkins, Second Edition will explain the advantages of combining Jenkins and Docker to improve the continuous integration and delivery process of an app development. It will start with setting up a Docker server and configuring Jenkins on it. It will then provide steps to build applications on Docker files and integrate them with Jenkins using continuous delivery processes such as continuous integration, automated acceptance testing, and configuration management.
Moving on, you will learn how to ensure quick application deployment with Docker containers along with scaling Jenkins using Kubernetes. Next, you will get to know how to deploy applications using Docker images and testing them with Jenkins. Towards the end, the book will touch base with missing parts of the CD pipeline, which are the environments and infrastructure, application versioning, and nonfunctional testing.
By the end of the book, you will be enhancing the DevOps workflow by integrating the functionalities of Docker and Jenkins.
Table of Contents (18 chapters)
Title Page
Dedication
About Packt
Contributors
Preface
Free Chapter
Introducing Continuous Delivery
Introducing Docker
Configuring Jenkins
Continuous Integration Pipeline
Automated Acceptance Testing
Clustering with Kubernetes
Configuration Management with Ansible
Continuous Delivery Pipeline
Advanced Continuous Delivery
Best practices
Assessment
Other Books You May Enjoy
Index
Customer Reviews