Pipery

Overview

Pipery is a vendor-neutral CI/CD standardization layer for reusable delivery workflows. It helps teams define pipeline logic once, run it across platforms such as GitHub Actions, GitLab CI, and Bitbucket Pipelines, and keep delivery workflows portable as platform choices change.

I built Pipery around a practical platform-engineering problem: teams repeatedly copy and maintain the same fragile CI/CD YAML across repositories, languages, and deployment targets. Pipery turns that repeated work into versioned, reviewed, reusable pipeline families.

What It Provides

• Reusable CI pipelines for Docker, Go, npm, Python, Java, C/C++, Rust, and Terraform projects
• Reusable CD pipelines for ArgoCD, Helm, Google Cloud Run, Ansible/AWX, Docker Compose/Swarm, and Terraform deployments
• Cross-platform workflow support across GitHub Actions, GitLab CI, and Bitbucket Pipelines
• Structured execution logs through psh, producing replayable pipery.jsonl output for debugging and observability
• Release and deploy bots for deliberate release branching, tagging, scheduled deployments, and auditability
• Dashboard tooling for analyzing pipeline execution data and understanding workflow failures

Engineering Focus

Pipery is designed as a developer-platform product, not just a collection of CI templates. The core concerns are portability, predictable upgrades, release safety, security review, and operational visibility.

The ecosystem includes a shared Go runtime, action-scaffolding and release tooling, Terraform-managed repository governance, release-tested action repositories, and a documentation site at pipery.dev.

Links