Accelerate your
CI pipelines
Create portable, lightweight pipelines that work the same on your local machine as they do in CI.
Get Started →-p-800.webp)
The fact that the CI/CD pipeline runs the same on my machine, your machine, the cloud is a big draw.
How Garden makes writing and running pipelines
✨ faster ✨
Before Garden vs. with Garden
Writing pipelines
Difficult-to-write pipelines:
Write each step of the CI pipeline hand.
Write each step of the CI pipeline hand.
Tedious test iteration: Repeatedly rerun the entire pipeline for every change.
Brittle pipelines: Break things whenever you change/add steps or restructure the pipeline.
Easy-to-write (and clear) pipelines: Declaratively describe your stack in terms of build, deploy, test, run.
Iterate at the speed of thought: Only rerun changed steps with smart test caching.
Dynamic pipelines: Adjust without fear! No need to change your CI config when you change your stack.
Running pipelines
Siloed pipeline: Your CI system is the only way to reliably build and deploy a realistic instance of your project.
Staging environment bottlenecks: No reliable, automated way to create a one-off environment from scratch.
Commit, push, wait: Wait for entire pipelines to be rerun even for the smallest changes.
Portable pipeline: Run Garden anywhere. Build, deploy and test from your laptop or your CI pipeline.
Ephemeral environment bliss: Spin up production-like environments as needed.
Accelerated pipelines: Version every build, deploy, and test step in your pipeline to rebuild, deploy, or test only changed code.
My experience with Garden has been fantastic.
It delivers on its promise of being a single blueprint for your services, handling build and deployment dependencies alike. It makes managing deployments to your various environments (prod, dev, QA, etc) simple.
It delivers on its promise of being a single blueprint for your services, handling build and deployment dependencies alike. It makes managing deployments to your various environments (prod, dev, QA, etc) simple.
Your CI/CD pipeline as code
Codify your stack with YAML declarations that describe how your system is built, deployed, and tested to create a portable blueprint that can run in CI or on your local machine.
Create one source of truth
Use the same tool and the same set of commands for across delivery, from source to finish.
Manage complex systems
Garden uses your Dockerfiles, Helm charts, Terraform stacks and more to weave together your dev & testing automation. We don’t shy away from complexity—we leverage it.
Leverage out-of-the-box gamechanging automations
When you codify your stack using Garden’s build, deploy, test, and run actions, each comes with powerful built-in automations — including in-cluster building and one-off runner pods for tests and scripts.
How Podium uses Garden to manage a complex stack
We now deploy and end-to-end test 130 services, hundreds of times per day. We could not have done that without Garden.
