Description

Goal: Close INFRA-3628 Phase 5b — make Namespace-hosted CI jobs use Namespace’s supported checkout path instead of treating them like GitHub-hosted runners, without changing how runner_provider: current behaves today.

What we shipped: Every place the workflow graph already chooses Namespace via runner_provider now checks out with nscloud checkout on namespace and keeps the existing actions/checkout path on current (same majors / if: guards so the default path stays equivalent). That covers the main ci graph, reusable builds and node-modules setup, iOS/Android E2E build workflows, the callable run-e2e-workflow runner, and the smoke/regression report jobs that also land on Namespace Linux when trialing Namespace.

E2E setup: The shared setup-e2e-env composite accepts optional yarn and CocoaPods per-attempt retry timeouts; run-e2e-workflow raises the outer Set up E2E environment cap for Namespace + iOS and passes those inputs so parallel iOS smoke is less likely to die mid-install under contention. This is a stability cushion; deeper Namespace CocoaPods cache work can follow the same ticket / INFRA-3596 thread.

Scope note: No app or product behaviour changes — CI and composite action YAML only.

Changelog

CHANGELOG entry: null

Related issues

Fixes: INFRA-3628

Manual testing steps

Feature: INFRA-3628 Namespace checkout pilot

  Scenario: Current runner path is unchanged
    Given ci (or downstream workflows) run with runner_provider current
    When checkout steps execute
    Then the same actions/checkout path runs as before and nscloud checkout is skipped

  Scenario: Namespace runner path uses nscloud checkout
    Given the same workflows run with runner_provider namespace
    When checkout steps execute
    Then nscloud checkout runs on Namespace profiles and actions/checkout is skipped

  Scenario: Namespace iOS E2E smoke can finish environment setup more often
    Given a Namespace dispatch with a full iOS smoke matrix
    When each shard runs Set up E2E environment
    Then setup is less likely to hit the previous hard timeout during CocoaPods under parallel load

Screenshots/Recordings

N/A — infrastructure / CI only.

Before

N/A

After

N/A

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable (validated via pull_request CI and Namespace workflow_dispatch trials on this branch)
• I've documented my code using JSDoc format if applicable (N/A — YAML / workflow config only)
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Performance checks (if applicable)

N/A — no app or bundle changes.

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.