Jenkins X Pipelines Internals

This is a series of blog posts on the internals of the Jenkins X Pipelines, implemented using Prow and Tekton.

As I am starting to migrate from the Jenkins Declarative Pipelines to the (new) Jenkins X Pipelines — defined in YAML format and implemented using Prow and Tekton — I am diving into the internals of the system, because I like to understand how things works.

So I am now sharing my findings here, as a series of blog posts. I’ll add links to source code so you can dive deeper into a specific topic if you want.

• The first part is a walk-through of a GitHub WebHook event coming to the cluster until it results in a running Tekton Pipeline. It explains how Prow understands the webhook event, “kind of” forwards it to Jenkins X, which retrieves the right pipeline to execute and translate it into a format that Tekton can understand. Read it here.
• The second part dives into the “Meta Pipeline”: the part of the workflow which is responsible for retrieving the right pipeline to execute, and to translate it into a format that Tekton can understand. Read it here.
• The third and fourth parts are focused on the stages and steps that compose a pipeline.

Coming soon…

• The release pipeline
• The pipelines scheduler
• The feedback loop
• …