Installation Through Operator #
The easiest way to install Pipelines-as-Code on OpenShift is with the Red Hat OpenShift Pipelines Operator.
On the OpenShift Pipelines Operator, the default namespace is openshift-pipelines
.
Note:
When Pipelines-as-Code is installed through the Tekton Operator the configurations of Pipelines-as-Code is
controlled by TektonConfig Custom Resource.
That means Tekton Operator will revert the configurations changes done directly on pipeline-as-code
configmap or OpenShiftPipelinesAsCode
custom resource.
The default configurations for Pipelines-as-Code in TektonConfig
looks like below
apiVersion: operator.tekton.dev/v1alpha1
kind: TektonConfig
metadata:
name: config
spec:
platforms:
openshift:
pipelinesAsCode:
enable: true
settings:
bitbucket-cloud-check-source-ip: 'true'
remote-tasks: 'true'
application-name: Pipelines-as-Code CI
auto-configure-new-github-repo: 'false'
error-log-snippet: 'true'
error-detection-from-container-logs: 'false'
hub-url: 'https://api.hub.tekton.dev/v1'
hub-catalog-name: tekton
error-detection-max-number-of-lines: '50'
error-detection-simple-regexp: >-
^(?P<filename>[^:]*):(?P<line>[0-9]+):(?P<column>[0-9]+):([
]*)?(?P<error>.*)
secret-auto-create: 'true'
secret-github-app-token-scoped: 'true'
remember-ok-to-test: 'true'
You can add or update all supported configuration keys for Pipelines-as-Code under settings
. After you change the TektonConfig
custom resource, the operator updates the configuration of your pipelines-as-code
configmap automatically.
Note:
By default, Tekton Operator installs Pipelines-as-Code, default value of enable
is true
as in the following example:
spec:
platforms:
openshift:
pipelinesAsCode:
enable: true
settings:
To disable installation of Pipelines-as-Code, you can set enable: false
as in the following example:
spec:
platforms:
openshift:
pipelinesAsCode:
enable: false
settings: