Pipelines as Code

Getting Started with Pipelines as Code

Pipelines as Code lets you define your CI/CD pipelines using Tekton PipelineRuns and Tasks in files stored directly alongside your source code — versioned, reviewed, and collaborated on just like your application code.

Why Pipelines as Code?

Git-native: Pipeline definitions live in a .tekton/ directory in your repo
Automatic PR checks: Pipeline runs trigger on pull requests and pushes, with status reported directly on the PR
Multi-provider: Works with GitHub, GitLab, Bitbucket, and Forgejo
GitOps commands: Control pipelines from PR comments — /retest, /test, /cancel
Automatic resolution: Tasks are resolved from your repo, Artifact Hub, or remote URLs

Get Started

The fastest way to try Pipelines as Code:

Install on a kind cluster or OpenShift Local:
```
tkn pac bootstrap
```
Create a repository with a .tekton/ directory containing your PipelineRun YAML.
Open a Pull Request and watch the pipeline run with status checks.

For the full walkthrough, see the Pipelines as Code Getting Started guide.

Learn More

Authoring Guide

Learn how to author and structure your pipeline definitions.

GitOps Commands

Control pipeline runs directly from PR comments.

Task Resolution

Automatic resolution from local files, Artifact Hub, and remote URLs.

Getting Started with Pipelines Tasks