Summary

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 file.
• The commit pipeline can be extended with the code quality stages.
• No matter what the project build tool, Jenkins commands should always be consistent with local development commands.
• Jenkins offers a wide range of triggers and notifications.
• The development workflow should be carefully...