Skip to content

chore: allow e2e port to be defined by env vars#16285

Merged
paulpopus merged 1 commit intomainfrom
chore/allow-e2e-port-to-be-defined-by-env-vars
Apr 15, 2026
Merged

chore: allow e2e port to be defined by env vars#16285
paulpopus merged 1 commit intomainfrom
chore/allow-e2e-port-to-be-defined-by-env-vars

Conversation

@paulpopus
Copy link
Copy Markdown
Contributor

Port number is currently hardcoded to 3000, this makes it so it defaults back to 3000 but you can override it via env vars. Helps when running lots of e2es in parallel with various agents by providing predictability.

@github-actions
Copy link
Copy Markdown
Contributor

📦 esbuild Bundle Analysis for payload

This analysis was generated by esbuild-bundle-analyzer. 🤖
This PR introduced no changes to the esbuild bundle! 🙌

Copy link
Copy Markdown
Member

@AlessioGr AlessioGr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is fine, but there are lots of other hardcoded ports that need updating within tests

@paulpopus paulpopus merged commit cb97614 into main Apr 15, 2026
334 of 337 checks passed
@paulpopus paulpopus deleted the chore/allow-e2e-port-to-be-defined-by-env-vars branch April 15, 2026 16:09
@github-actions
Copy link
Copy Markdown
Contributor

🚀 This is included in version v3.83.0

milamer pushed a commit to milamer/payload that referenced this pull request Apr 20, 2026
Port number is currently hardcoded to 3000, this makes it so it defaults
back to 3000 but you can override it via env vars. Helps when running
lots of e2es in parallel with various agents by providing
predictability.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants