…rence

Mounting APK output dirs directly as nscloud cache volumes prevents
Gradle from deleting/recreating them during packageProdRelease:
  Unable to delete directory 'android/app/build/outputs/apk/prod/release'

Move APK cache to ~/.namespace-apk-cache/ (a dedicated staging area
on the cache volume). On cache hit, APKs are copied FROM staging TO
the Gradle output dirs. After a successful build, APKs are copied TO
staging and the marker is recorded. This avoids mount interference
while preserving APK reuse across Namespace runs.

Co-authored-by: Cursor <cursoragent@cursor.com>

…stence

The separate ~/.namespace-apk-cache/ path was not persisting between
Namespace runs despite being listed in nscloud-cache-action. The cache
volume grew (184MB -> 501MB) but the staging dir contents were empty
on the second run.

Move staging to $GRADLE_USER_HOME/apk-cache/ which is a subdirectory
of an already-persisted cache path (GRADLE_USER_HOME/caches and
/wrapper are confirmed to persist). This avoids relying on a
standalone new path that nscloud may not handle correctly.

Co-authored-by: Cursor <cursoragent@cursor.com>

Co-authored-by: Cursor <cursoragent@cursor.com>

Add nsc cache gradle setup step that generates an init script with
workspace-scoped short-term credentials. The script is placed in
$GRADLE_USER_HOME/init.d/ so it auto-loads on every ./gradlew
invocation without modifying scripts/build.sh.

This enables cross-run Gradle task reuse: first run populates the
remote cache (slow), subsequent runs reuse cached build outputs
(fast). Works alongside the existing nscloud-cache-action for
dependency downloads (local cache volumes for JARs/plugins).

Per Namespace docs and updated INFRA-3597 acceptance criteria.

Co-authored-by: Cursor <cursoragent@cursor.com>

…caching

Replace custom GRADLE_USER_HOME/caches and /wrapper paths with the
native cache: gradle support in nscloud-cache-action. The native
framework support handles Gradle dependency paths automatically and
may use a different persistence mechanism that resolves the cache
miss issue we've been seeing with custom path entries.

This works alongside the Gradle remote build cache (nsc cache gradle
setup) — Cache Volumes handle downloaded dependencies (JARs, plugins),
remote cache handles compilation outputs and task results.

Co-authored-by: Cursor <cursoragent@cursor.com>

… gradle

The native cache: gradle targets ~/.gradle/ but our GRADLE_USER_HOME
is /home/runner/_work/.gradle/ -- different paths. Gradle writes deps
to the custom location but the native cache mounts at the default,
so deps are never cached and Maven Central returns 429 on every cold
run.

Add both: cache: gradle for the default ~/.gradle (future-proofing)
plus explicit GRADLE_USER_HOME/caches and /wrapper for our custom
location. Belt and suspenders until GRADLE_USER_HOME is standardized.

Co-authored-by: Cursor <cursoragent@cursor.com>

Per Namespace team guidance: add maven cache mode alongside gradle to
ensure Maven dependency downloads (including plugins from Maven Central)
are retained in ~/.m2/repository across runs. This avoids repeated
bulk downloads that trigger HTTP 429 rate limiting from
repo.maven.apache.org on cold-cache builds.

Even after Namespace ships their in-house Maven mirrors, this local
caching remains beneficial as it skips downloads entirely.

Co-authored-by: Cursor <cursoragent@cursor.com>

…esting

Co-authored-by: Cursor <cursoragent@cursor.com>

…testing

Co-authored-by: Cursor <cursoragent@cursor.com>

…te limits

Co-authored-by: Cursor <cursoragent@cursor.com>

…id E2E on namespace

Mount the same cache volume paths (Gradle, Maven, Yarn, node_modules,
apk-cache) in E2E shards so the post-step commit preserves the build
job's cached data instead of overwriting it with an empty state.

Limit Android E2E on namespace to SmokeAccounts (1 shard) to validate
cache volume persistence end-to-end before enabling the full matrix.
iOS E2E remains skipped on namespace.

Co-authored-by: Cursor <cursoragent@cursor.com>

Only mount absolute Gradle paths in the E2E shard so its post-step
commit does not overwrite the build job's heavier node_modules/yarn
cache with a lighter fresh-install version.

Co-authored-by: Cursor <cursoragent@cursor.com>

Match find-reusable-build: empty fingerprint omits source identity from the
marker; do not run Namespace APK cache hit logic in that case.

Co-authored-by: Cursor <cursoragent@cursor.com>