It is essentially to spend time building a robust CICD pipeline. This allows for rapid deployments and feature velocity, while maintaining quality gates.

In the sample, we triggered the pipeline manually. However, as described earlier, we should configure web hooks to trigger the pipeline on code pushes. The GitHub steps for setting in this are are pretty straight forward. Navigate to the Webhooks & Services tab and choose Configure Services. Find the Jenkins (GitHub plugin) option and fill it with the URL to your Jenkins server, which should be something like http://<Name of Jenkins server>:8080/github-webhook/. Make sure to tick the Active checkbox and ensure things work by using the Test Hook button: