chore(repo): parallelize e2e-ci tasks on large/xlarge agents

[FrozenPandaz]

Current Behavior

Many e2e-ci projects are pinned to serial execution on each CI agent via project-specific overrides in .nx/workflows/dynamic-changesets.yaml:

• e2e-gradle, e2e-angular, e2e-node, e2e-react → 1 task per linux-extra-large
• e2e-next, e2e-plugin → 2 tasks per linux-extra-large
• e2e-release, e2e-nuxt, e2e-web, e2e-eslint, e2e-remix, e2e-cypress, e2e-docker, e2e-js, e2e-nx, e2e-nx-init, e2e-dotnet, e2e-workspace-create, e2e-rollup → 1 on large / 2 on xlarge

These overrides exist because the underlying tests collide on hardcoded ports when run concurrently on the same agent.

Expected Behavior

A single rule lets every e2e-ci** task run with parallelism 2 on linux-large and 3 on linux-extra-large, shrinking total agent time and removing per-project special cases.

To make that safe, this PR:

1. Adds reservePort()/reservePorts() to e2e/utils/port-utils.ts. The helper claims a port via an atomic O_EXCL lock file under /tmp/nx-e2e-port-locks, so two parallel processes on the same agent cannot reserve the same port. The existing getAvailablePort() is deprecated — probing port 0 and then binding it seconds later opens a TOCTOU race where another e2e task could grab the same port in between.
2. Replaces hardcoded ports in the highest-risk e2e tests with reservePort():
   • e2e/vite/src/vite.test.ts — serve-static test (was 8081)
   • e2e/web/src/web-webpack.test.ts — webpack ssl serve (was 5000)
   • e2e/storybook/src/storybook-angular.test.ts and storybook-nested.test.ts (was 4400)
   • e2e/node/src/node-server.test.ts — express/fastify/koa/nest framework tests (was 7000–7003) and waitUntilTargets test (was 4444/4445)
   • e2e/node/src/node-esm-support.test.ts — 9 tests previously defaulting to port 3000

e2e/cypress, e2e/playwright, and the React module-federation tests still hardcode ports through their generators; those will be addressed in follow-up PRs as CI surfaces collisions.

Related Issue(s)

N/A — internal CI optimization.

[netlify]

👷 Deploy Preview for nx-dev processing.

Name	Link
🔨 Latest commit	74ae9b9
🔍 Latest deploy log	https://app.netlify.com/projects/nx-dev/deploys/69f8be92254a490009a435b6

[netlify]

✅ Deploy Preview for nx-docs ready!

Name	Link
🔨 Latest commit	74ae9b9
🔍 Latest deploy log	https://app.netlify.com/projects/nx-docs/deploys/69f8be9220b34400087a91f8
😎 Deploy Preview	https://deploy-preview-35325--nx-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 74ae9b9

Command	Status	Duration	Result
nx affected --targets=lint,test,build,e2e,e2e-c...	✅ Succeeded	20m 50s	View ↗
nx run-many -t check-imports check-lock-files c...	✅ Succeeded	3s	View ↗
nx-cloud record -- pnpm nx-cloud conformance:check	✅ Succeeded	16s	View ↗
nx build workspace-plugin	✅ Succeeded	<1s	View ↗
nx-cloud record -- nx sync:check	✅ Succeeded	23s	View ↗
nx-cloud record -- nx format:check	✅ Succeeded	8s	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-05-04 18:19:17 UTC

[nx-cloud]

✅ The fix from Nx Cloud was applied

We introduced a separate reservePort() call for the esbuild standalone app serve so each serve command holds its own atomic lock-file-backed port, rather than reusing the already-released appPort. This prevents a parallel e2e task on the same agent (enabled by this PR's increased parallelism) from binding to the freed OS port before the second serve starts, which was causing the "Port already in use" failure.

Tip

✅ We verified this fix by re-running e2e-angular:e2e-ci--src/projects-build-and-test.test.ts.

Suggested Fix changes

diff --git a/e2e/angular/src/projects-build-and-test.test.ts b/e2e/angular/src/projects-build-and-test.test.ts
index 6e1b0edb..d61a092d 100644
--- a/e2e/angular/src/projects-build-and-test.test.ts
+++ b/e2e/angular/src/projects-build-and-test.test.ts
@@ -105,15 +105,16 @@ describe('Angular Projects - Build and Test', () => {
     // port and process cleanup
     await killProcessAndPorts(process.pid, appPort);
 
+    const esbuildPort = await reservePort();
     const esbProcess = await runCommandUntil(
-      `serve ${esbuildStandaloneApp} -- --port=${appPort}`,
+      `serve ${esbuildStandaloneApp} -- --port=${esbuildPort}`,
       (output) =>
         output.includes(`Application bundle generation complete`) &&
-        output.includes(`localhost:${appPort}`)
+        output.includes(`localhost:${esbuildPort}`)
     );
 
     // port and process cleanup
-    await killProcessAndPorts(esbProcess.pid, appPort);
+    await killProcessAndPorts(esbProcess.pid, esbuildPort);
   }, 1000000);
 
   it('should successfully work with rspack for build', async () => {

  

View interactive diff ↗

_{🎓 Learn more about Self-Healing CI on nx.dev}