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

[test] Run CircleCI anytime #22676

Merged
merged 1 commit into from Sep 21, 2020
Merged

[test] Run CircleCI anytime #22676

merged 1 commit into from Sep 21, 2020

Conversation

eps1lon
Copy link
Member

@eps1lon eps1lon commented Sep 21, 2020

Branch filters are not as granular as with azure. We can't differentiate between pull requests and pushes with the branch name. Only PRs from other remotes follow the pull/* branch naming scheme.

The current only and old ignore didn't make sense since it would've prevented any CircleCI run (which we currently see on dependabot PRs).

CircleCI should still auto-cancel builds on any branch but the default branch. If we continue to see large queues for the l10n_* branches then we should contact support.

Ideally we want:

  • build every commit for master and next
  • build the latest commit for open PRs

So l10n_next would only build once a PR is open and auto-cancel on new commits. This is how azure pipelines and netlify deploys work so I don't understand why CircleCI works different.

@eps1lon eps1lon added the test label Sep 21, 2020
@mui-pr-bot
Copy link

No bundle size changes comparing 27ada08...5a00e40

Generated by 🚫 dangerJS against 5a00e40

@eps1lon eps1lon merged commit 5440c77 into mui:next Sep 21, 2020
@eps1lon eps1lon deleted the test/circle-ci-filter branch September 21, 2020 09:49
eps1lon added a commit to eps1lon/material-ui that referenced this pull request Sep 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants