-
Book Overview & Buying
-
Table Of Contents
-
Feedback & Rating

Jenkins Administrator's Guide
By :

In this chapter, we've learned how to control user roles and permissions based on folders, which allows multiple teams to share a Jenkins instance. We've created a static pipeline equipped with unit tests and code coverage, and their outputs were nicely presented on the Jenkins UI. We've converted the static pipeline into a premerge CI pipeline that is triggered by GitHub PR activities, which allows us to validate the changes before a PR is merged. Finally, we've protected the Git repository's main
branch by requiring a successful premerge build for a merge.
In the coming chapter, we will expand on the same idea and build a more advanced postmerge CD pipeline. Our work on advanced pipelines will feature practical activities such as versioning, Git tagging, Docker image creation, and pushing using Docker-out-of-Docker (DooD or DinD depending on the context).