Fast, Portable CI Pipelines that Run Anywhere
Last updated
Was this helpful?
Docs Edge
Last updated
Was this helpful?
If you find yourself waiting for an entire CI pipeline to re-run just because you updated a commit message, Garden might be the tool for you. It can be the difference between hours and minutes across all stages of software delivery.
Teams typically use Garden to run tests, create preview environments, and share team namespaces in long-lived Kubernetes clusters. The more teams use Garden, the faster your CI pipelines become because everyone contributes to a shared cache. This is particularly useful for end-to-end tests, which are often the longest running tests in CI.
Similarly, when developers run the test from their laptop, Garden will also skip running it in CI. Since the test runs in a remote environment and Garden knows the version of every single file, they can trust that the test does indeed pass. No need to run it again.
Simply by adding extra environments to your Garden project, you can use Garden for local development and for testing and deploying your project in CI.
Cached builds and tests: Garden caches your tests and builds so you only run what has changed. The result is dramatic reductions for CI run-times, typically twenty minutes to an hour.
Automatic environment cleanup, deep Insights into CI test, builds and deploys, and triggered CI runs with
Encode once, run anywhere: can be run from any environment, including local machines, CI servers, and cloud environments.
Visualize your CI/CD flow: Use the to visualize your CI/CD pipeline, view logs, and track command history.
Accelerate build times: With remote image builds, you can speed up your image build times significantly.
If you're already familiar with Garden and just want to get going, click any of the links above to set up your features.
Garden's
Garden's official .
Join our 🌸 for access to Garden's dedicated Community Engineers and our AI chatbot 🤖 trained on our docs.