foForgeRock
GitHubping-javascript-sdkWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionSucceeded
      security-deps-updates
    • Runs and Agents
    • Configuration
    • Self-Healing CI
    • Project Graph
    • Circular DependenciesEnterprise
    • Resource Usage
    • Analysis
    • ConformanceEnterprise
  • Runs
    • Current runSucceeded
    • Tasks
    • Resource Usage
Insights
  • Compare tasks
  • Analytics
    fix(ci): pin e2e suites to dedicated Nx Cloud agent groups Both e2e suites' apps share port 5829 (CORS prevents distinct ports), so atomized e2e-ci tasks from both suites could interleave on the same Nx Cloud agent. A leaked dev server would then be wrongly reused across suites. Assignment rules isolate each suite's e2e-ci tasks to dedicated agents: davinci/journey e2e tasks now route to isolated agent pools (using the linux-medium-js template, as custom template names are not supported — the rules still create separate per-suite agent allocations).
    nx run-many -t build --no-agents
Succeeded
Linux
4 CPU cores
read access token used
1c8ca4f3815
100%

Cache hits

22 of 22 tasks used cache.

Protect cache integrity with sandboxing

Get faster results

Learn how to enable distribution.

Atomizer enabled

19 groups of tasks optimized.

See resource usage for your runs

Add the resource usage add-on to record CPU and memory per task on your run's main agent and trace slow runs or out-of-memory failures to the task that caused them.

Add resource usage

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools
GitHubping-javascript-sdkWorkspace