Check what's new with Namespace.
Aggregate Cache Volume Usage
You can now check your cache volume usage over the last 45 days from the storage tab. It includes both your daily cache at rest use, as well as the total active-cache use and finally your cache hit ratio.
More robust Cache volumes
We've deployed a number of changes that have improved the user experience of using Cache Volumes. The biggest change being that we guarantee every run now has enough disk space to generate a complete cache. This addresses the biggest piece of feedback: not being in a situation where you run out of disk space before you've stored all of the requested cache size.
No more team seat limits
We've removed team seat limits from plans. It was an arbitrary limit which was preventing collaboration. Add as many team members to your workspace as you need. Feature billing follows a usage based model. Check our Pricing
information for more.
Multiple Builders per Workspace
For users with high loads of concurrent Docker Builds, Namespace Workspaces can now have multiple Builder instances per architecture. This feature enables load balancing of build requests across available Builder instances, ensuring predictable performance and reliable builds. Reach out at email@example.com
if you'd like to have this enabled for your Workspace.
Automatically grow your cache volumes to have a minimum configurable amount of disk space at start. This helps you strike a balance between effective cache sizes, and ensuring that your workloads have enough disk space to do what they have to do.
Protected Branches for Cache Volumes
With Protected Branches, you can designate a set of branches as primary branches (e.g. your main branch would be a primary branch); only pushes to primary branches perform updates to the cache contents, protecting caches from being poisoned with changes that are part of PRs. With Protected Branches, your PRs still get up-to-date caching, which is cloned from the last cache commit.
Build cross references
Namespace now surfaces cross references between builds, CI runs, and instances. Easily and quickly navigate from a CI run to any builds it triggered to check their logs and traces, and vice-versa.
Cache Action Modes
Select languages and frameworks to cache with
nscloud-cache-action, or continue to cache any file you want.
Cache Volume lineage
Understand which volumes are attached to your instances. And hover a volume to reveal its lineage.
Custom Runner Images
Reduce GitHub Workflow time by creating your own custom runner image with pre-installed Ubuntu packages.
Build Trace Viewer is now in GA
Every Docker build handled by Namespace's Remote Builders gets its own trace view. You can intuitively debug why a particular build didn't perform as you expected.
Buildkite, GitHub and Federation integrations can now be modified by all users of a workspace.
Introducing Cache Volumes
Cache volumes run on local, high-performance storage allowing them to vastly outperform remote caching solutions.
Automatic Kubernetes Previews
Namespace can automatically generate previews for your Kubernetes applications. Namespace’s ingress manager observes annotations on your services to expose previews automatically.
Introducing Build Trace Viewer
Every Docker build handled by Namespace's Remote Builders now gets its own trace view. You can now more intuitively debug why a particular build didn't perform as you expected.
Review our Changelog Blog entries for updates prior to July 4th, 2023.