An opinionated CI based on Tekton.
Pipelines as Code lets you define your CI/CD using Tekton PipelineRuns and Tasks in files stored directly alongside your source code. Your pipeline definitions are versioned, reviewed, and collaborated on just like your application code — bringing the full power of the Git workflow to your CI/CD pipelines. With a single pane of glass from your SCM provider (GitHub, GitLab, Bitbucket, or Forgejo), pipeline runs are automatically triggered for Pull Requests and Push events.
Set up your first pipeline in minutes
Understand the architecture and key components
Learn how to author and run pipelines
GitHub, GitLab, Bitbucket, Forgejo
tkn-pac commands
Repository CR, ConfigMap, and settings
Features
Pull-request status support with GitHub Checks API, including rechecks for Pull Request and Push events.
When you open or update a pull request, Pipelines as Code shows status checks (like pass/fail) directly on the PR, so you can see at a glance whether your pipeline succeeded. It can re-run these checks automatically when you push new commits or update the PR.
Pull-request actions through comments —
/retest, /test, /cancel, and more.You can control pipelines directly from PR comments: type
/retest to re-run failed checks, /test to run a specific pipeline, /cancel to stop a run, and more—no need to leave the PR page or use separate tools.Automatic Task resolution from local files, Artifact Hub, and remote URLs.
Pipelines as Code can automatically find and use your pipeline definitions from your repository, from Artifact Hub, or from a remote URL—so you don’t have to paste long YAML files into a UI; it discovers and runs the right pipeline automatically.
GitHub App, GitHub Webhook, GitLab, Bitbucket Cloud, Bitbucket Data Center, and Forgejo.
Works with the Git platform you already use: GitHub (App or Webhook), GitLab, Bitbucket Cloud, Bitbucket Data Center, and Forgejo—so you can keep your existing workflow and still get all the benefits of Pipelines as Code.
Git event filtering with separate pipelines for each event type.
You can run different pipelines for different events (for example, only on push to main, or only on pull requests), so your CI stays fast and relevant to what actually changed in your code.
tkn-pac CLI plugin for bootstrapping, managing repos, and debugging.The
tkn-pac command-line tool helps you set up new repositories, manage Pipelines as Code configurations, and debug pipeline runs—all from your terminal without needing to navigate web interfaces.Getting Started
The easiest way to get started is to use tkn pac bootstrap on a Kind cluster or OpenShift Local environment. See the Getting Started guide for
step-by-step instructions.