Don't run long-running regression tests on PRs #3875
Merged
Conversation
This file contains 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
…to run every PR, but are still useful to run on master
hawkowl
added
size-small
hawkowl
requested review from
jewzaam,
bennerv,
rogbas,
petrkotas,
jharrington22,
cblecker,
cadenmarchese,
UlrichSchlueter,
SudoBrendan,
yjst2012,
jaitaiwan,
anshulvermapatel,
hlipsig,
tiguelu,
SrinivasAtmakuri,
mociarain,
kimorris27,
tsatam,
bitoku and
fahlmant
as code owners
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
E2E was 85m down from 113 :) |
tsatam
approved these changes
Oct 1, 2024
SrinivasAtmakuri
approved these changes
Oct 1, 2024
bitoku
approved these changes
Oct 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does / why we need it:
This runs regression tests on CI runs (i.e. tags and master) but does not run them during PRs, which cuts 20-30 minutes from the runtime.
Test plan for issue:
E2E changes, hopefully just works according to the docs
Is there any documentation that needs to be updated for this PR?
Comments are added in the relevant code
How do you know this will function as expected in production?
E2E tests, doesn't touch production