[v3-2-test] Skip UI E2E tests on derived full tests needed, canary, and scheduled builds (#64673)#64675
Merged
Merged
Conversation
…nd scheduled builds (#64673) UI E2E tests are expensive and should only run when UI files actually changed or the "full tests needed" label is explicitly set. Previously they ran on every push to main, canary build, scheduled run, and any PR that triggered derived full_tests_needed (env file changes, large PRs, etc.). (cherry picked from commit b15a5c9) Co-authored-by: Jarek Potiuk <[email protected]>
1 task
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
choo121600,
ephraimbuddy,
gopidesupavan,
jason810496,
jedcunningham,
jscheffl and
potiuk
as code owners
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 8, 2026
…nd scheduled builds (#64673) (#64675) UI E2E tests are expensive and should only run when UI files actually changed or the "full tests needed" label is explicitly set. Previously they ran on every push to main, canary build, scheduled run, and any PR that triggered derived full_tests_needed (env file changes, large PRs, etc.). (cherry picked from commit b15a5c9) Co-authored-by: Jarek Potiuk <[email protected]>
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
…nd scheduled builds (#64673) (#64675) UI E2E tests are expensive and should only run when UI files actually changed or the "full tests needed" label is explicitly set. Previously they ran on every push to main, canary build, scheduled run, and any PR that triggered derived full_tests_needed (env file changes, large PRs, etc.). (cherry picked from commit b15a5c9) Co-authored-by: Jarek Potiuk <[email protected]>
vatsrahul1001
added
the
changelog:skip
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
…nd scheduled builds (#64673) (#64675) UI E2E tests are expensive and should only run when UI files actually changed or the "full tests needed" label is explicitly set. Previously they ran on every push to main, canary build, scheduled run, and any PR that triggered derived full_tests_needed (env file changes, large PRs, etc.). (cherry picked from commit b15a5c9) Co-authored-by: Jarek Potiuk <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
UI E2E tests are expensive and should only run when UI files actually
changed or the "full tests needed" label is explicitly set. Previously
they ran on every push to main, canary build, scheduled run, and any
PR that triggered derived full_tests_needed (env file changes, large
PRs, etc.).
(cherry picked from commit b15a5c9)
Co-authored-by: Jarek Potiuk [email protected]