Meta tags:
description= Namespace accelerates the development workflow of fast-moving software engineering teams. Best-in-class compute and development-supporting services that lead to 2x-10x faster builds, tests, and more.;
Headings (most frequently used words):
android, set, up, emulators, getting, started, full, example, gradle, build, cache, related, documentation, introducing, devboxes, we, re, hiring, join, us, create, runner, profile, caching, jdk, and, sdk, run, the, emulator,
Text of the page (most frequently used words):
nsc (74), #android (31), cache (27), gradle (21), setup (16), github (16), actions (14), profile (14), name (13), with (12), namespacelabs (12), action (12), uses (11), set (11), nscloud (11), namespace (10), emulator (9), list (9), registry (9), artifact (9), docker (9), build (8), run (8), tests (8), caching (7), for (6), runner (6), use (6), the (6), and (6), image (6), describe (6), base (6), overview (6), your (5), dependencies (5), java (5), linux (5), create (5), emulators (5), token (5), builds (4), volumes (4), kvm (4), init (4), script (4), api (4), reactivecircus (4), runs (4), sdk (4), checkout (4), using (4), amd64 (4), started (4), login (4), vault (4), upload (4), buildx (4), instance (4), machine (3), support (3), gradlew (3), connectedcheck (3), x86_64 (3), arch (3), level (3), version (3), jdk (3), getting (3), runners (3), auth (3), update (3), download (3), ingress (3), expose (3), kubernetes (3), container (3), remote (3), images (3), devboxes (3), shapes (2), platform (2), dev (2), virtualization (2), tmp (2), workflow (2), share (2), outputs (2), this (2), temurin (2), distribution (2), jobs (2), example (2), required (2), resources (2), hardware (2), performance (2), status (2), trust (2), generate (2), delete (2), sccache (2), pants (2), bazel (2), expiration (2), extend (2), volume (2), git (2), job (2), access (2), ssh (2), logs (2), usage (2), circleci (2), security (2), limits (2), storage (2), custom (2), logo (2), open (2), last, updated, april, 2026, speed, available, configurations, integration, nested, related, documentation, dependency, both, addition, you, can, also, across, complementary, while, store, downloaded, stores, compilation, task, results, repository, steps, pull_request, main, branches, push, here, complete, running, full, start, install, tooling, faster, then, created, label, enabled, enough, good, starting, point, vcpu, ram, named, profiles, recommend, dedicated, workflows, backed, are, currently, supported, additional, when, that, accelerated, enables, fast, testing, without, penalty, software, emulation, acceleration, center, soc2, changelog, revoke, relationships, check, add, default, policy, url, expire, release, submodules, test, optimize, cleanup, attach, context, kubectl, kubeconfig, write, port, forward, proxy, rdp, vnc, top, report, destroy, workspace, installation, cli, turbocache, breakpoint, cluster, explorer, dashboard, rwx, openid, gcp, aws, federation, permissions, audit, logging, data, residency, billing, workspaces, egress, filtering, networking, secrets, resource, display, observability, windows, macos, compute, any, framework, tailscale, claude, checkouts, nix, moonrepo, playwright, turborepo, integrations, coding, agents, sessions, development, managing, introduction, containers, previews, tracing, builders, reference, optimizing, migration, guide, debugging, roles, hiring, join, read, article, introducing, sidebar, get, company, pricing, customers, cases,
Text of the page (random words):
android emulators namespace logo use cases customers pricing resources company get started login open sidebar introducing devboxes read article we re hiring join us open roles logo overview github actions getting started caching docker builds custom base images debugging github actions migration guide optimizing usage reference docker builders getting started container registry tracing logs previews containers kubernetes devboxes introduction managing devboxes remote development sessions custom images coding agents integrations bazel turborepo playwright android emulators gradle sccache circleci pants moonrepo nix git checkouts docker images claude tailscale any framework compute overview linux macos windows observability ssh remote display machine shapes resource limits storage overview cache volumes container registry artifact storage secrets networking overview ingress performance security egress filtering workspaces overview access billing and limits data residency security audit logging permissions federation overview aws gcp openid github actions circleci rwx dashboard github actions builds registry usage explorer api sdk github actions namespacelabs nscloud setup namespacelabs nscloud setup buildx action namespacelabs nscloud cluster action namespacelabs nscloud cache action namespacelabs nscloud checkout action namespacelabs nscloud expose kubernetes action namespace actions upload artifact namespace actions download artifact namespacelabs breakpoint action namespace actions setup turbocache cli installation nsc version nsc login nsc workspace describe nsc create nsc destroy nsc extend nsc list nsc instance report nsc logs nsc top nsc ssh nsc vnc nsc rdp nsc proxy nsc instance port forward nsc instance download nsc instance upload nsc kubeconfig write nsc kubectl nsc docker login nsc docker attach context nsc docker remote nsc docker buildx setup nsc docker buildx cleanup nsc docker buildx status nsc build nsc base image upload nsc base image optimize nsc run nsc expose container nsc expose kubernetes nsc ingress list nsc ingress generate access token nsc github profile nsc github profile create nsc github profile list nsc github profile describe nsc github profile update nsc github profile delete nsc github profile test build base image nsc github base image list nsc github base image describe nsc github job list nsc github job describe nsc git checkout update submodules nsc volume list nsc volume release nsc artifact upload nsc artifact download nsc artifact expire nsc artifact extend nsc artifact describe nsc artifact cache url nsc registry list nsc registry describe nsc registry share nsc registry update image expiration nsc registry policy nsc registry default expiration nsc cache bazel setup nsc cache gradle setup nsc cache pants setup nsc cache sccache setup nsc vault list nsc vault add nsc vault set nsc vault delete nsc auth check login nsc auth generate dev token nsc auth trust relationships nsc token create nsc token list nsc token revoke changelog trust center soc2 status support android emulators run android emulators with hardware acceleration on namespace runners namespace runners support hardware accelerated android virtualization using kvm this enables fast android emulator testing without the performance penalty of software emulation kvm backed android emulators are currently supported on linux amd64 runners linux amd64 no additional kvm setup is required when using that platform getting started create a runner profile we recommend using a dedicated profile for android emulator workflows go to your runner profiles and create a profile named namespace profile android with linux amd64 linux amd64 enough resources for your emulator 4 vcpu x 8 gb ram is a good starting point caching enabled to cache gradle dependencies then use the created profile as your runs on label jobs android tests runs on namespace profile android set up caching use namespacelabs nscloud cache action to cache gradle dependencies for faster builds name set up gradle cache uses namespacelabs nscloud cache action v1 with cache gradle set up jdk and android sdk use actions setup java and android actions setup android to install the required tooling name set up jdk uses actions setup java v4 with distribution temurin java version 17 name set up android sdk uses android actions setup android v3 run the emulator start an emulator and run your tests for example by using the reactivecircus android emulator runner action name run android tests uses reactivecircus android emulator runner v2 with api level 30 arch x86_64 script gradlew connectedcheck full example here s a complete workflow for running android tests name android tests on push branches main pull_request jobs android tests runs on namespace profile android steps name checkout repository uses namespacelabs nscloud checkout action v7 name set up gradle cache uses namespacelabs nscloud cache action v1 with cache gradle name set up jdk uses actions setup java v4 with distribution temurin java version 17 name set up android sdk uses android actions setup android v3 name run android tests uses reactivecircus android emulator runner v2 with api level 30 arch x86_64 script gradlew connectedcheck gradle build cache in addition to caching gradle dependencies with cache volumes you can also use namespace s gradle build cache to share build outputs across runs this is complementary to caching dependencies while cache volumes store downloaded dependencies the gradle build cache stores compilation outputs and task results to use both in your workflow name set up gradle dependency cache uses namespacelabs nscloud cache action v1 with cache gradle name set up gradle build cache run nsc cache gradle setup init gradle tmp init gradle name run android tests uses reactivecircus android emulator runner v2 with api level 30 arch x86_64 script gradlew init script tmp init gradle connectedcheck related documentation nested virtualization platform support for dev kvm gradle integration gradle build caching machine shapes available machine configurations caching speed up builds with cache volumes last updated april 10 2026
|