Skip to content
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

Merged
merged 1 commit into from
May 8, 2024

Conversation

nolanlawson
Copy link
Contributor

Details

Refreshes our required Nucleus downstreams based on

  1. Low flakiness
  2. Tests not taking too long
  3. Team ownership, no individual repos

Spreadsheet with analysis based on last 10 runs

Does this pull request introduce a breaking change?

  • 😮‍💨 No, it does not introduce a breaking change.

Does this pull request introduce an observable change?

  • 🤞 No, it does not introduce an observable change.

@nolanlawson nolanlawson requested a review from a team as a code owner May 8, 2024 18:05
milestone-.*: # used for prerelease testing
pull-request:
<<: *branch-definition
workflow: build-and-test # the default workflow is release, and we just want build+tests
Copy link
Contributor Author

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
Copy link
Contributor Author

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.

Copy link
Member

@ekashida ekashida left a 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.

@nolanlawson
Copy link
Contributor Author

One is due to container tests, the other to e2e tests.

@nolanlawson
Copy link
Contributor Author

/nucleus ignore --reason 'flaky downstreams are flaky'

@nolanlawson nolanlawson merged commit 035ead9 into master May 8, 2024
10 checks passed
@nolanlawson nolanlawson deleted the nolan/nucleus-refresh-2 branch May 8, 2024 20:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants