-
Notifications
You must be signed in to change notification settings - Fork 16
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
Bug 1907217: remove *
branch from RelEng github repositories and maple
#18
Bug 1907217: remove *
branch from RelEng github repositories and maple
#18
Conversation
f7480ce
to
e7835b9
Compare
Failure is just an intermittent that is being fixed in #30 |
projects.yml
Outdated
- name: "*" | ||
level: 1 |
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.
For the staging / level 1 repos, we may actually want to remove the main
/master
branch and keep just *
?
AFAIK using the default branch is only necessary when we want to change actions, but for everything else using other branches is probably better (less chance of collision)?
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.
Hm, I think that's probably reasonable. If we're doing that, we should probably keep a level 1 *
branch in level 3 repos as well (I keep going back and forth on whether or not that's a good idea...but I don't think it does any harm).
AFAIK using the default branch is only necessary when we want to change actions, but for everything else using other branches is probably better (less chance of collision)?
Can you clarify what you mean by "less chance of collision"? I'm not sure I see how it connects to the rest of the comment.
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.
I don't think this applies to the same extent to other repos, where there's only a couple of branches we care about and the rest are pretty much only used for PRs, which get their own graphs.
For the staging repos though the entire point is to make arbitrary changes without going through PRs. I think of those a bit like try, where each push is basically its own mercurial head, and branch names are irrelevant.
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.
If you're exclusively talking about staging repos, yeah, I agree those are different. If we're talking about non-staging level 1 repos as well (of which there are many that aren't staging), I'm not sure I see those as any different from level 3 repos.
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.
I was thinking about the staging repos specifically, yes. Sorry for the confusion.
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.
Oh sure - yes. Let's do that.
…ry` r?#releng-reviewers! Stage one of the plan written out in the bug. This _should_ be quite safe. For Maple, all of the scopes that `branch:*` has are already granted by `branch:default`. For GitHub we have some differences, but as far as I can tell, only where the explicit branches have more scopes than `branch:*` due to grants such as https://github.com/mozilla-releng/fxci-config/blob/944ea85da779ab430e932f9829f1f02bb11ee11c/grants.yml#L1185-L1200. Original revision/discussion in https://phabricator.services.mozilla.com/D216239
e7835b9
to
80713fd
Compare
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.
lgtm, thanks!
This depends on a handful of PRs to these repos: mozilla-mobile/reference-browser#2982 mozilla-mobile/firefox-ios#21357 mozilla/code-review#2289 mozilla/code-coverage#2408 mozilla/translations#777 After this change, the only Github repositories with `*` branches will be `staging` repositories, as was discussed in mozilla-releng#18.
This depends on a handful of PRs to these repos: mozilla-mobile/reference-browser#2982 mozilla-mobile/firefox-ios#21357 mozilla/code-review#2289 mozilla/code-coverage#2408 mozilla/translations#777 After this change, the only Github repositories with `*` branches will be `staging` repositories, as was discussed in mozilla-releng#18.
This also adds branches to a couple of repositories where I noticed we were missing one that the build on. This depends on a handful of PRs to these repos: mozilla-mobile/reference-browser#2982 mozilla-mobile/firefox-ios#21357 mozilla/code-review#2289 mozilla/code-coverage#2408 mozilla/translations#777 After this change, the only Github repositories with `*` branches will be `staging` repositories, as was discussed in mozilla-releng#18.
This also adds branches to a couple of repositories where I noticed we were missing one that the build on. This depends on a handful of PRs to these repos: mozilla-mobile/reference-browser#2982 mozilla-mobile/firefox-ios#21357 mozilla/code-review#2289 mozilla/code-coverage#2408 mozilla/translations#777 After this change, the only Github repositories with `*` branches will be `staging` repositories, as was discussed in mozilla-releng#18.
This also adds branches to a couple of repositories where I noticed we were missing one that the build on. This depends on a handful of PRs to these repos: mozilla-mobile/reference-browser#2982 mozilla-mobile/firefox-ios#21357 mozilla/code-review#2289 mozilla/code-coverage#2408 mozilla/translations#777 After this change, the only Github repositories with `*` branches will be `staging` repositories, as was discussed in mozilla-releng#18.
This also adds branches to a couple of repositories where I noticed we were missing one that the build on. This depends on a handful of PRs to these repos: mozilla-mobile/reference-browser#2982 mozilla-mobile/firefox-ios#21357 mozilla/code-review#2289 mozilla/code-coverage#2408 mozilla/translations#777 After this change, the only Github repositories with `*` branches will be `staging` repositories, as was discussed in mozilla-releng#18.
#46) This also adds branches to a couple of repositories where I noticed we were missing one that the build on. This depends on a handful of PRs to these repos: mozilla-mobile/reference-browser#2982 mozilla-mobile/firefox-ios#21357 mozilla/code-review#2289 mozilla/code-coverage#2408 mozilla/translations#777 After this change, the only Github repositories with `*` branches will be `staging` repositories, as was discussed in #18.
Stage one of the plan written out in the bug.
This should be quite safe. For Maple, all of the scopes that
branch:*
has are already granted bybranch:default
.For GitHub we have some differences, but as far as I can tell, only where the explicit branches have more scopes than
branch:*
due to grants such asfxci-config/grants.yml
Lines 1185 to 1200 in 944ea85
Original revision/discussion in https://phabricator.services.mozilla.com/D216239
ci-admin diff
for this is in https://gist.github.com/bhearsum/61df6555dea05bebb9c12b491d6259ce