-
Notifications
You must be signed in to change notification settings - Fork 382
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(nucleus): refresh required downstreams #4203
Conversation
milestone-.*: # used for prerelease testing | ||
pull-request: | ||
<<: *branch-definition | ||
workflow: build-and-test # the default workflow is release, and we just want build+tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was something I was messing around with at some point but stopped doing.
@@ -8,21 +8,28 @@ branches: | |||
auto-start: true | |||
auto-start-from-forks: false | |||
merge-method: disabled # do not auto-merge; we'll do it ourselves | |||
validate-optional-downstream-deps: true # temporarily test non-required downstreams |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This increases our overall execution cost with low value, unless we're actively doing this kind of flakiness analysis. We can turn this back on next time we want to refresh this list.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did we check what the issue was for salesforce-experience-platform-emu/lightning-components
and communities/webruntime
? Looks like they only failed once but wondering if it's due to a flaky test or an env issue.
One is due to container tests, the other to e2e tests. |
/nucleus ignore --reason 'flaky downstreams are flaky' |
Details
Refreshes our required Nucleus downstreams based on
Spreadsheet with analysis based on last 10 runs
Does this pull request introduce a breaking change?
Does this pull request introduce an observable change?