GitOps-Driven CI Pipeline with GitHub

With Jenkins up and running, it's time to create pipelines.

We will create two projects, an adder and a subtractor, then create users with varying permissions to understand the roles and permissions model. We will also create a static pipeline that compiles the code, runs unit tests, and generates a code coverage report.

Afterward, we will convert the static pipeline into a premerge CI pipeline that is triggered by GitHub pull requests (PRs). Building a trigger for AWS Jenkins is different from firewalled Jenkins due to network restrictions, so we'll cover both options in depth.

Once the build is complete, the original GitHub PR that triggered the build is updated with the result. We'll also configure ...

Get Jenkins Administrator's Guide now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.