In this chapter, we covered all aspects of the Continuous Integration pipeline, which is always the first step for Continuous Delivery. Here are the key takeaways:
The pipeline provides a general mechanism for organizing any automation processes; however, the most common use cases are Continuous Integration and Continuous Delivery. Jenkins accepts different ways of defining pipelines, but the recommended one is the declarative syntax. The commit pipeline is the most basic Continuous Integration process and, as its name suggests, it should be run after every commit to the repository.
The pipeline definition should be stored in the repository as a Jenkinsfile. The commit pipeline can be extended with the code-quality stages. No matter the project build tool, Jenkins commands should always be consistent with the local development commands.
Jenkins offers a wide range of triggers...
