Big news! We’re releasing Garden 0.14 and launching the next generation of Garden Cloud—the first step in a huge evolution for Garden.
What’s new
- Remote Container Builder general access
No more slow local builds! Now, every Garden Cloud user gets access to powerful remote build acceleration, previously only available in Enterprise plans. - The new Garden Team Tier
A dedicated, collaborative experience for teams scaling with Garden. - Team-wide caching
Cache test results across clusters and environments with team-wide caching in Garden Cloud. - A new Builds UI
Get deep visibility into your build performance and optimize with ease.
You can take advantage of all of these new features whether you have a paid account or not. For more details on the different plans we offer, see the Garden plans page.
Remote Container Builder for all
This release added a new Team Tier, but all of the new features are available to free and paid accounts alike. Chief among these is Remote Container Builder, which gives you access to ephemeral cloud compute resources for your builds.
For more details, see the Remote Container Builder documentation.
Longtime Garden users will notice that the web UI looks quite a bit different from previous versions and comes with new capabilities. In the first iteration, we’re specifically focusing on helping teams spend less time waiting on container builds.
With the new "Builds" UI, you’ll be able to analyze where your container builds are spending the most time. Plus, our Remote Container Builder allows your entire team to benefit from blazing-fast build compute instances, caching the results of the layers of your Dockerfile on low-latency, high-throughput NVMe storage.
One temporary change to note: in this first release, command results and logs won’t be displayed as they were in the previous version. But don’t worry—we’re working hard to bring them back as soon as possible!
In general, we’re investing heavily in the new Garden Cloud product and you can expect to see rapid improvements.
What’s changed
In 0.14, we're changing the cache backend we use for our Kubernetes-based Test and Run actions (i.e. `kubernetes-pod`, `helm-pod` and `container` Runs and Tests).
In 0.13 and earlier, results for these action types were cached using ConfigMaps created in the Kubernetes cluster being used. This has worked well for a long time, but came with certain problems and limitations. ConfigMaps would pile up over time, requiring administrators to periodically clean them up. Also, tests couldn't be cached across Kubernetes clusters, which made it impossible to get cache hits for tests in CI that had already been successfully run e.g. on a local Kubernetes cluster during development.
Our solution to this was to use Garden Cloud as the caching backend. This means zero maintenance for our users, and more importantly, opens the door to fully shared caching across environments.
0.14 also contains several deprecations and breaking changes that are intended to make Garden easier to adopt and use.
Please see our release notes for 0.14 for a full list of changes. We're sure you'll love the new & improved Garden you'll experience in 0.14!
Check out the new Garden
To use the new cloud version after the release, you’ll need update Garden to version 0.14 and sign in again at app.garden.io. Check out our documentation for more details.
Stay tuned, and if you have any questions, don’t hesitate to join us on Discord.
If you’re new to Garden, and want to see Garden Cloud in action, there’s no better time to get started!
