chore: Run MMI tests on long-running branches #28651
Merged
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.
Description
The
check_mmi_trigger.sh
script has been updated to run MMI-related tests on long-running branches (develop
,master
, and RCs). This is intended to make it easier for us to detect these regressions sooner, so that we don't waste time tracking down the commit that caused any given breakage.Related issues
No linked issue. This is intended to make it safer to extend the use of this MMI filter to other jobs, which will help us save CircleCI credits
Manual testing steps
I tested this locally by running the script with the
CIRCLE_PULL_REQUEST
,GITHUB_TOKEN
, andCIRCLE_BRANCH
environment variables set. e.g.Screenshots/Recordings
N/A
Pre-merge author checklist
Pre-merge reviewer checklist