Pipelines-as-Code is an opinionated CI/CD solution built on OpenShift Pipelines and Tekton. It enables you to define, manage, and execute pipelines directly from your source code repository.
📖 Full documentation: pipelinesascode.com
🛠️ Development branch docs: here
Pipelines-as-Code follows the Pipelines-as-Code methodology, bringing it directly to Tekton and OpenShift Pipelines.
- ✅ Pull Request status support – Automatically updates PR status during pipeline execution.
- 🔄 GitHub Checks API – Recheck and validate your pipelines effortlessly.
- 🔗 GitHub PR & Commit Events – Trigger pipelines via pull requests, pushes, and commits.
- 💬 PR Actions in Comments – Use
/retestand other commands for better control. - 📂 Event-based Pipelines – Define different pipelines for different Git events.
- ⚡ Automatic Task Resolution – Supports local tasks, Tekton Hub, and remote URLs.
- 📦 Efficient Config Retrieval – Uses GitHub blobs & objects API to fetch configs.
- 🔐 Access Control – Manage via GitHub orgs or Prow-style
OWNERfiles. - 🛠️
tkn-pacCLI Plugin – Easily manage Pipelines-as-Code repositories. - 🌍 Multi-Git Support – Works with GitHub (via GitHub App & Webhook), GitLab, Gitea, Bitbucket Data Center & Cloud via webhooks.
Head over to the Documentation for the full feature list and detailed guides:
The easiest way to get started is using the tkn pac CLI and its bootstrap command.
We have a full walk-through tutorial here:
https://pipelinesascode.com/docs/install/getting-started/
This guide will guide you through the installation process and help you set up your first Pipelines-as-Code repository.
We ❤️ contributions!
If you'd like to help improve Pipelines-as-Code, check out our contribution guide: Contribute Here.
🔔 Join the Community:
- 📅 Subscribe to the community calendar
- 💬 Chat on Slack: #pipelinesascode (Join TektonCD Slack)
-
📝 Latest Developer Documentation: Main branch docs