ci: Use distributed Nx agents for e2e tests

[lachlancollins]

This changes the "test:e2e" tasks to run on the distributed Nx agents, rather than on its own GitHub job. This means the tasks are cached and parallelised optimally.

Unfortunately, this isn't compatible with the "@replayio/playwright" setup (it uses the standard "@playwright/test" setup), but I'm not sure how much this was being used - if this is a necessary part of the workflow, then this change won't work.

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 1b83944. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 2 targets

• nx affected --targets=test:format,test:eslint,test:unit,test:e2e,test:types,test:build,build --parallel=3
• nx run-many --target=build --exclude=examples/**

---

Sent with 💌 from NxCloud.

[pkg-pr-new]

Run & review this pull request in StackBlitz Codeflow.

commit: 1b83944

@tanstack/history

npm i https://pkg.pr.new/@tanstack/history@1911

@tanstack/react-cross-context

npm i https://pkg.pr.new/@tanstack/react-cross-context@1911

@tanstack/react-router

npm i https://pkg.pr.new/@tanstack/react-router@1911

@tanstack/react-router-with-query

npm i https://pkg.pr.new/@tanstack/react-router-with-query@1911

@tanstack/router-cli

npm i https://pkg.pr.new/@tanstack/router-cli@1911

@tanstack/router-devtools

npm i https://pkg.pr.new/@tanstack/router-devtools@1911

@tanstack/router-generator

npm i https://pkg.pr.new/@tanstack/router-generator@1911

@tanstack/router-plugin

npm i https://pkg.pr.new/@tanstack/router-plugin@1911

@tanstack/router-vite-plugin

npm i https://pkg.pr.new/@tanstack/router-vite-plugin@1911

@tanstack/start

npm i https://pkg.pr.new/@tanstack/start@1911

@tanstack/start-vite-plugin

npm i https://pkg.pr.new/@tanstack/start-vite-plugin@1911

---

templates

• tanstack-router-react-example-authenticated-routes
• tanstack-router-react-example-basic
• tanstack-router-react-example-basic-default-search-params
• tanstack-router-react-example-basic-file-based
• tanstack-router-react-example-basic-file-based-codesplitting
• tanstack-router-react-example-react-query
• tanstack-router-react-example-basic-react-query-file-based
• tanstack-router-react-example-basic-ssr-file-based
• tanstack-router-react-example-basic-ssr-streaming-file-based
• tanstack-router-react-example-deferred-data
• tanstack-router-react-example-kitchen-sink
• tanstack-router-react-example-kitchen-sink-file-based
• tanstack-router-react-example-kitchen-sink-react-query
• tanstack-router-react-example-kitchen-sink-react-query-file-based
• tanstack-router-react-example-large-file-based
• tanstack-router-react-example-location-masking
• tanstack-router-react-example-navigation-blocking
• tanstack-router-react-example-quickstart
• tanstack-router-react-example-quickstart-file-based
• tanstack-router-react-example-quickstart-rspack-file-based
• tanstack-router-react-example-quickstart-webpack-file-based
• tanstack-router-react-example-scroll-restoration
• tanstack-router-example-react-start-basic
• tanstack-router-example-react-start-basic-counter
• tanstack-router-example-react-start-basic-react-query
• tanstack-router-example-react-start-basic-rsc
• tanstack-router-example-react-start-basic-trellaux
• tanstack-router-react-example-with-trpc-react-query
• tanstack-router-react-example-waku-rsc
• tanstack-router-react-example-with-bling
• tanstack-router-react-example-with-framer-motion
• tanstack-router-react-example-with-trpc

[SeanCassiere]

Currently, it's a good sanity check to make sure the Start examples (start-basic and start-basic-react-query), still work correctly after changes have been made to any of our packages. In the future, we should probably expand it to crawl our kitchen-sink or quickstart examples as well.

The replay.io is quite useful for actually watching the playback of what happened during the tests (especially in the failed cases).

@lachlancollins from what I can gather, this run only failed because an API key was missing. Could the job, not inherit the API key from the workflow?

Also, @jasonLaster @callingmedic911, could you please reconfirm that having this particular API key being publicly viewable is OK? And do we need different API keys for each example project? Currently, on the replay dashboard I'm only seeing the tests being recorded for start-basic but not the ones for start-basic-react-query.

[SeanCassiere]

Closing for now

[jasonLaster]

@SeanCassiere Yes - it's fine for the API key to be publicly available