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 affected -t build lint test typecheck e2e-ci
Succeeded
read access token used
1c8ca4f3815
90%

Cache hits

111 of 124 tasks used cache.

Protect cache integrity with sandboxing
63%

Distribution saved time

1m 01s instead of 2m 46s.

Atomizer enabled

25 groups of tasks optimized.

Resource usage is collected per agent

Run-level metrics are not available for distributed runs. View CPU and memory in this CI pipeline execution’s Analysis page.

© 2026 - Nx Cloud

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