This is the second part of the “Configure Laravel 8 for CI/CD with Jenkins and GitHub” story.

In the first part, I discussed some lessons I learnt from the “Continuous Delivery with Docker and Jenkins — Second edition” book (Chapters 1 to 5). It was about applying unit tests, code coverage tests, and acceptance tests for a Laravel 8 project (CI/CD). In that case, we used Amazon AWS, Jenkins, GitHub and Docker. Part 1 can be found here: https://medium.com/@danielgara/configure-laravel-8-for-ci-cd-with-jenkins-and-github-part-1-58b9be304292

In the second part, I’m going to introduce how to finish the CI/CD process (based on some elements I took from Chapters 6 to 8 of the Continuous Delivery book). In this case, we will make some modifications to the code presented in part 1, and we will design and implement a complete pipeline, which will allow us to release the new Laravel project versions in a production environment. The complete process can be found in Figure 1.

Figure 1. Complete CI/CD process

0. New concepts introduction

Ansible is the simplest way to automate apps and IT infrastructure. Application Deployment + Configuration Management + Continuous Delivery.

Smoke tests are a subset of test cases that cover the most important functionality of a component or system, used to aid assessment of whether main functions of the software appear to work correctly. It determines whether the deployed build is stable or not.

#jenkins #php #docker #laravel #continuous-delivery