Custom Pipelines Definition
Custom pipeline definitions in CodeNOW are managed through a dedicated Git repository that belongs to the account. This repository is the single source of truth for all custom Tekton pipelines defined for the account.
How It Works
Changes pushed to the custom pipelines repository are automatically synchronized to the cluster via ArgoCD. ArgoCD continuously watches the repository and applies any new or updated pipeline definitions to the Tekton installation running in the cluster. There is no manual deployment step — committing a pipeline definition to the repository is sufficient for it to become available in the cluster.
Accessing the Repository
The Custom Pipelines Definition menu item links directly to the account's custom pipelines Git repository. The repository contains a README.md that describes how to create and structure custom pipeline definitions for this account.
Access to the custom pipelines repository is restricted to account owners and administrators. Only users with these roles can push new or updated pipeline definitions to the repository.
Start with the README.md in the repository for instructions on the expected directory structure, naming conventions, and available pipeline templates specific to your account setup.
For inspiration when writing custom pipelines, browse the built-in CodeNOW pipeline definitions in the Tekton Dashboard at https://cn.<cluster-domain>/ci. The left menu exposes:
- Pipelines — all pipelines available to Tekton
- Tasks — all tasks that can be used within pipelines
- TriggerTemplates — trigger template definitions used to trigger all configured pipelines
For reference documentation on writing Tekton pipelines and tasks, see the Tekton documentation.