pipelines-as-code) contains global settings that apply to all repositories unless overridden at the repository level.
Location
The ConfigMap is typically installed in thepipelines-as-code namespace:
Configuration Fields
Application Settings
The application name used in status updates and comments. If using the GitHub App, you will need to customize this label in the GitHub App settings as well.
Secret Management
Whether to automatically create a secret with the token to be used by git-clone.
By default, only generate tokens scoped to the repository from where the payload comes from. This is important when the GitHub app is installed on a GitHub organization with a mix of public and private repositories where some users do not have access.Set to
false if you trust every user in your organization to access any repos or are not planning to install your GitHub application globally on a GitHub Organization.If you don’t want to completely disable the scoping of the token but still want some other repos (on the same installation ID) available from the token, add extra owner/repo here.You can have multiple owner/repositories separated by commas.
Hub Configuration
The default hub URL to use for fetching remote tasks.
The default hub catalog type. Supported values:
artifacthub, tektonhub.Additional hub catalogs configuration. You can configure multiple catalogs by incrementing the number (catalog-1-, catalog-2-, etc.).
Allow fetching remote tasks from configured hubs.
Dashboard Integration
URL of the Tekton dashboard. Pipelines as Code generates URLs to PipelineRuns on the Tekton dashboard using this base URL.
Name of a custom console to use instead of the Tekton dashboard.
Base URL of the custom console.
Template URL for PipelineRun details. Supports variables:
{{ namespace }}, {{ pr }}.Template URL for task logs. Supports variables:
{{ namespace }}, {{ pr }}, {{ task }}.Error Detection and Logging
Enable or disable the feature to show a log snippet of the failed task when there is an error in a Pipeline.You may want to disable this if you think your pipeline may leak sensitive values.
Number of lines to display in error log snippets when
error-log-snippet is set to true.The GitHub Check interface has a 65,535 character limit, so consider using a conservative value.Enable or disable inspection of container logs to detect error messages and expose them as annotations on Pull Requests. Only GitHub Apps is supported.
How many lines to grab from the container when inspecting logs for error detection. Increasing this value may increase the watcher memory usage. Use
-1 for unlimited lines.The default regexp used for simple error detection. Must be a valid regular expression.
Concurrency Control
Global setting to control whether Pipelines as Code should automatically cancel any in-progress PipelineRuns associated with a pull request when that pull request is updated. This helps prevent multiple redundant runs from executing simultaneously.
Global setting to determine whether Pipelines as Code should automatically cancel in-progress PipelineRuns triggered by a push event if a new push occurs on the same branch. This prevents overlapping or redundant runs for the same branch.
Bitbucket Cloud Settings
Since public Bitbucket doesn’t have the concept of webhook secrets, secure requests by querying https://ip-ranges.atlassian.com/. This only happens for public Bitbucket (when provider.url is not set in repository spec).
Add extra IPs (e.g.,
127.0.0.1) or networks (e.g., 127.0.0.0/16) separated by commas.Retention Policies
Defines the upper limit for the
max-keep-run annotation value which a user can set on a PipelineRun. The value set on the annotation should be less than or equal to the upper limit; otherwise, the upper limit will be used while cleaning up.If defined, applies to all PipelineRuns that don’t have the
max-keep-runs annotation.Auto-Configuration
Whether to auto-configure newly created repositories. This will create a new namespace and Repository CR. Supported only with GitHub App.
Template to generate the namespace name for an auto-configured GitHub repository. Supported fields:
{{repo_owner}}, {{repo_name}}.Template to generate the Repository CR name for an auto-configured GitHub repository. Supported fields:
{{repo_owner}}, {{repo_name}}.Security and Authorization
Enable or disable the feature to re-run the CI if a push event happens on a pull request after
/ok-to-test has been done once.By default it is false, meaning /ok-to-test should be done on each iteration. Set to true to remember the approval across push events.Enforces that a pull request’s commit SHA must be specified in an
/ok-to-test comment. This prevents a race condition where a malicious user could push a bad commit after the /ok-to-test comment is posted but before the CI runs.When enabled, prevents duplicate pipeline runs when a commit appears in both a push event and a pull request. If a push event comes from a commit that is part of an open pull request, the push event will be skipped.
Complete Example
Updating Configuration
To update the ConfigMap:Most ConfigMap changes take effect immediately, but some may require restarting the Pipelines as Code controller.