Pipelines on JayeX - Cloud Native CI/CD Built On Kubernetes

Demo

Mon, 01 Jan 0001 00:00:00 +0000

Demo

The following demo walks through how to trigger tekton pipelines and create custom pipelines:

Editing

Mon, 01 Jan 0001 00:00:00 +0000

Source layout

If you upgrade your cluster to the latest version stream then you will find if you create a new quickstart that:

.lighthouse/jenkins-x directory contains the default CI/CD pipelines for JayeX with these files:
- triggers.yaml to define the lighthouse TriggerConfig which defines the ChatOps and triggering configuration via a spec field which defines presubmits and postsubmits (i.e. Pull Request and Release triggers).
- pullrequest.yaml defines the Pull Request pipeline using a Tekton Task, Pipeline or PipelineRun
- release.yaml defines the Release pipeline using a Tekton Tekton Task, Pipeline or PipelineRun
jenkins-x.yml files are no longer used by default in new quickstarts instead we use the above. Note if you have projects using jenkins-x.yml files they are still supported if you import them into v3 or you can use this tool to migrate them to tekton pipelines

Catalog

Mon, 01 Jan 0001 00:00:00 +0000

As we create more and more software we tend to get an explosion in the number of git repositories and microservices. Each repository needs automated CI and CD; but how do we manage the hundreds of pipelines we need - while also making it easy to share pipelines across repositories and allowing each repository to customize when required?

JayeX solves this as follows:

the pipelines, tasks and steps are defined via Tekton YAML letting you use any tekton tooling such as IDE completion and validation
we support an image: uses:sourceURI notation that lets you inherit steps from a git repository without having to copy/paste the source code aross repositories.

For example if you create a new quickstart pipeline may look like this (slightly condensed)…

Debugging

Mon, 01 Jan 0001 00:00:00 +0000

Warning

TaskRun breakpoint functionality is no longer supported since Tekton 0.29.0 upgrades in 3.2.298. For more info see Kubernetes 1.22 - Breaking change!.

Here is a demo which shows how to debug pipelines:

Prerequisites

Make sure your cluster is upgraded to the latest version stream.

If you intend to use the jx in the below examples make sure you upgrade the CLI too

Enable a breakpoint

To enable a breakpoint you can:

Upgrading

Mon, 01 Jan 0001 00:00:00 +0000

Converting older pipelines

If you have older pipelines in your git repository created with an older version of JayeX you can convert them to the new concise image: uses:sourceURI syntax via the jx pipeline convert command:

jx pipeline convert

The pipelines should be modified and if you have a Kptfile it will be removed.

If you have any old jenkins-x.yml files, those will be converted across to the new .lighthouse tekton notation too.