Skip to content

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Apr 7, 2021

Limits the various snapshot tests to only run against the main branch. They are very likely to fail against the older branches, because by definition Angular's latest changes at HEAD might not be backwards-compatible.

@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent merge safe target: patch This PR is targeted for the next patch release labels Apr 7, 2021
@crisbeto crisbeto requested a review from a team as a code owner April 7, 2021 18:47
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Apr 7, 2021
@crisbeto crisbeto force-pushed the main-branch-snapshots branch 2 times, most recently from 0c5d398 to 304537b Compare April 7, 2021 18:54
- view_engine_snapshot_test_cronjob
- mdc_snapshot_test_cronjob
- snapshot_tests_local_browsers:
filters: *only_main_branch_filter
Copy link
Member Author

Choose a reason for hiding this comment

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

Disclaimer: I don't actually know if this will work as expected, I'm basing it on how we've dealt with similar situations in other places. As far as I can tell, there's no good way of testing it without merging in the changes.

Copy link
Member

Choose a reason for hiding this comment

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

I tried parsing the config and it looks like this needs to be indented as above with other jobs using filters.

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks, updated 👍

@crisbeto crisbeto force-pushed the main-branch-snapshots branch from 304537b to 1d5d038 Compare April 7, 2021 19:37
Limits the various snapshot tests to only run against the main branch. They are very likely to main against the older branches, because by definition Angular's latest changes at HEAD might not be backwards-compatible.
@crisbeto crisbeto force-pushed the main-branch-snapshots branch from 1d5d038 to 637fd6b Compare April 7, 2021 19:38
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Apr 7, 2021
@mmalerba mmalerba merged commit 5f00365 into angular:master Apr 8, 2021
mmalerba pushed a commit that referenced this pull request Apr 8, 2021
Limits the various snapshot tests to only run against the main branch. They are very likely to main against the older branches, because by definition Angular's latest changes at HEAD might not be backwards-compatible.

(cherry picked from commit 5f00365)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators May 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants