Settings

Pipelines-as-Code uses two layers of configuration that work together:

Global configuration

The pipelines-as-code ConfigMap in the pipelines-as-code namespace controls cluster-wide behavior: authentication defaults, Hub catalogs, error detection, retention policies, concurrency, and more.

See the ConfigMap Reference for all fields and their default values.

For instructions on viewing and applying changes, see Configuration.

Per-repository configuration

Each Repository CR can include a spec.settings block that overrides selected global defaults for that repository. This covers provider-specific options, concurrency limits, and pipeline event policies.

See the Repository CR Settings Reference for all fields.

Configuration inheritance

When both layers define the same setting, the Repository CR value takes precedence for that repository. Global settings apply wherever no Repository CR override is present.

See Global Repository Settings for details on the inheritance model and how to configure shared defaults using a global Repository CR.

Status information

Pipelines-as-Code exposes read-only status through the pipelines-as-code-info ConfigMap in the pipelines-as-code namespace. Any authenticated user can read this ConfigMap. It contains:

• version — the installed version of Pipelines-as-Code
• controller-url — the controller URL configured during bootstrap or by the operator
• provider — the detected provider type (for example, GitHub App)