PikoCI Documentation¶
PikoCI is a portable, self-hosted CI/CD system. One binary, any database, runs anywhere.
Get started¶
- Getting Started - Install and run your first pipeline
- Pipeline Reference - HCL pipeline configuration
- CLI Reference - Client commands and flags
Core concepts¶
- Resource Types - Built-in and custom resource types
- Runners - Built-in and custom runners
- Secret Types - Built-in and custom secret types
- Services - Ephemeral per-job services
- Notifications - Fire-and-forget notifications (GitHub checks, Slack, Discord)
- Variables - Pipeline variables
- Functions - HCL functions available in pipelines (Terraform-compatible)
- for_each and matrix - Generate multiple job instances from a single definition
Security & access¶
- Roles & Permissions - Team roles and what each role can do
- Authentication - Local login, OAuth/OIDC single sign-on
- API Tokens - Non-interactive authenticated access for scripts and CI/CD
- Approval Gates - Require human approval before jobs run
- Audit Log - Track who did what within a team
Operations¶
- Server Configuration - Server flags and options
- Database Backends - Supported database systems
- Scaling - From single binary to distributed production
- Running Workers Separately - Distributed worker setup
- Deployment - Production deployment guide
- Pause / Unpause - Temporarily stop pipelines or jobs
- Resource Pinning - Pin resources to a version and trigger with specific versions
- Public Pipelines - Sharing pipeline status publicly
Migration & portability¶
- Portability and Bundling - Bundle and deploy anywhere
- Coming from Concourse - Migration guide for Concourse users