Check out what’s new in OpenShift Pipelines 1.8
A cloud-native continuous integration and continuous delivery (CI/CD) solution built on Kubernetes resources are Red Hat OpenShift Pipelines 1.8. It abstracts away the underlying implementation details to automate deployments across several platforms using Tekton building blocks. For developing CI/CD pipelines that work with all Kubernetes distributions, Tekton presents a set of common custom resource definitions (CRDs).
On OpenShift Container Platform 4.10, Red Hat OpenShift Pipelines 1.8 is now generally available. It is also scheduled to be made available on 4.11 and 4.12.
New Features and Enhancements in Open Shift Pipelines 1.8:
Red Hat OpenShift Pipelines on Arm:
With this update, you can use an OpenShift Container Platform cluster that uses Arm architecture to run Red Hat OpenShift Pipelines 1.8 and later.
Tekton Hub enhancements:
- As an administrator, you can set up Tekton Hub to use a different database than the one that comes with it.
- If you enable Tekton Hub as an administrator, it will periodically refresh the catalog with the most recent data. The duration of this time period is configurable.
- Because Tekton Hub offers improved default configuration options, administrators can deploy it quickly and easily. You can begin utilizing Tekton Hub while consulting with your teams to determine what customizations they require.
Pipelines as code enhancements:
Add Git repository via webhook:
Using the webhook technique, you can add your Git repository to Pipelines as Code. In this approach, Pipelines as Code can be used even if GitHub Apps is not practical.
Trigger multiple pipelines for one Git event:
For a single git event, such as a PR, you can start more than one pipeline run.
Manual and third-party triggers:
Developers won’t have to be constrained by a code flow in order to initiate pipelinerun.
Support for additional git providers like Gitlab and Bitbucket Bootstrapping via dev console:
- From the dev console, you can create a Github application. In (Figure 1)
- By adding repositories, you can set the git provider (GitHub, GitLab, and BitBucket) to enable pipeline as code. (Figure 2)
As we are deprecating the tekton.dev/v1alpha1 API version, support for the PipelineResource custom resource (CR) and Condition custom resource (CR) has been removed in addition to the features indicated above.
Please see the Release Notes section of the OpenShift Documentation for a complete list and more information on each component of this release.