Repo menu: Use a separate repository group for the rentable twig repos

RESOLVED FIXED

Status

P2
normal
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: emorley, Assigned: KWierso)

Tracking

Details

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Currently the "development" repository group includes repos such as mozilla-central, mozilla-inbound etc (which is fine), but also includes the releng rentable repos such as cedar, ash, oak. In addition there are teams that have semi-active team repos that perhaps don't belong alongside mozilla-inbound etc.

I'm thinking that it would be good to distinguish between mozilla-central et al and cedar/ash/... for the purposes of:
* making the repos menu clearer (ie having a separate list for both)
* assigning permissions (when we have more granular treeherder permissions in the future)
* assigning job exclusion profiles to one group but not the other

I'm thinking perhaps we could call the new repo group "project", ie:

development:
* mozilla-central
* mozilla-inbound
* fx-team
* gaia-master
...

project:
* ash
* cedar
* services-central
...

@sheriffs: Thoughts?
(Reporter)

Updated

4 years ago
Blocks: 1053985
(Reporter)

Updated

4 years ago
No longer blocks: 1030636
(Reporter)

Updated

4 years ago
Summary: Use a separate repository group for the rentable twig repos → Repo menu: Use a separate repository group for the rentable twig repos
(Assignee)

Comment 1

4 years ago
Created attachment 8486607 [details] [review]
Move twigs and other project branches into their own category

In theory, this splits all of the twigs and a few other project repos out to their own category. I haven't tested this at all, but it looked right to me.
Attachment #8486607 - Flags: review?(cdawson)

Updated

4 years ago
Attachment #8486607 - Flags: review?(cdawson) → review+
(Reporter)

Comment 2

4 years ago
https://github.com/mozilla/treeherder-service/commit/5c7b827883954c5e5aa430bb3f08649c2b113d36
Assignee: nobody → kwierso
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.