Closed
Bug 1387640
Opened 7 years ago
Closed 7 years ago
Use Tiers instead of exclusion profiles
Categories
(Tree Management :: Treeherder, enhancement, P1)
Tree Management
Treeherder
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: camd, Assigned: camd)
References
(Blocks 1 open bug)
Details
Attachments
(3 files)
Some sub-bugs that should come from this bug are:
1. Stop applying a Tier to TaskCluster jobs based on exclusion profiles. Just use the value that is specified in the task definition. Tier-3 jobs are hidden.
2. Create a white or black list in the Treeherder codebase ETL layer for jobs from BuildBot that will be hidden. These jobs will be set to Tier-3
3. Create a similar list for Buildbot Tier-2 jobs. The only Buildbot Tier-2 jobs I can find on m-i, m-c and autoland are Autophone and Talos. So this should be a pretty short list.
The proposal for this is a work-in-progress since it can have wide-ranging effects:
https://docs.google.com/document/d/1-BzCN97aCZKovWeh1zU6ASyp_FVtg0mbITN7C_iWXzg/edit#heading=h.dhpfyfxjvgg9
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → cdawson
Assignee | ||
Comment 1•7 years ago
|
||
Hidden Taskcluster Jobs:
Looks like funsize and valgrind jobs need to be set to Tier-3
mozilla-central: https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&exclusion_profile=default&visibility=excluded&filter-tier=1&filter-tier=2&filter-tier=3&filter-build_system_type=taskcluster
None of the rest of these have any hidden TC jobs when I checked just now:
mozilla-inbound: https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&exclusion_profile=default&visibility=excluded&filter-tier=1&filter-tier=2&filter-tier=3&filter-build_system_type=taskcluster
try: https://treeherder.mozilla.org/#/jobs?repo=try&exclusion_profile=default&visibility=excluded&filter-tier=1&filter-tier=2&filter-tier=3&filter-build_system_type=taskcluster
autoland: https://treeherder.mozilla.org/#/jobs?repo=try&exclusion_profile=default&visibility=excluded&filter-tier=1&filter-tier=2&filter-tier=3&filter-build_system_type=taskcluster
Comment 2•7 years ago
|
||
Bug 1390192 is another example of how the new way will mean less confusion all around.
CCing Andrew, since it sounds like we all want the same thing:
https://groups.google.com/forum/#!topic/mozilla.tools.treeherder/ygqPmBob3Z0
Assignee | ||
Comment 3•7 years ago
|
||
I'm going to start working on this bug this month, so bumping to P1.
Priority: -- → P1
Assignee | ||
Updated•7 years ago
|
Assignee | ||
Comment 4•7 years ago
|
||
The first PR for bug 1398386 will switch so the ingestion sets tiers for jobs, including Tier-3 for buildbot jobs that should be hidden.
The second PR will make the /jobs endpoint stop checking the exclusion profiles and remove the models for excluding. It will also remove using the exclusion param from the UI.
Comment 5•7 years ago
|
||
Assignee | ||
Comment 6•7 years ago
|
||
Comment on attachment 8907260 [details] [review]
[treeherder] mozilla:remove-exclusion-profiles-2 > mozilla:master
This will be followed up by a PR that removes all the models and tables for exclusion profiles. I just wanted to leave them intact juuuuust in case there was a problem.
Attachment #8907260 -
Flags: review?(emorley)
Comment 7•7 years ago
|
||
Comment on attachment 8907260 [details] [review]
[treeherder] mozilla:remove-exclusion-profiles-2 > mozilla:master
(In reply to Cameron Dawson [:camd] from comment #6)
> I just wanted to leave them intact juuuuust in case there was a problem.
Good idea :-)
Attachment #8907260 -
Flags: review?(emorley) → review+
Comment 8•7 years ago
|
||
Commit pushed to master at https://github.com/mozilla/treeherder
https://github.com/mozilla/treeherder/commit/bde8e20f1f950c8edb953b1278b33575cc45da72
Bug 1387640 - Stop using exclusion profiles
Note: This leaves the models and tables intact so that we can
revert without data loss in case we discover an issue. A follow-up
commit will remove those tables and models.
Updated•7 years ago
|
Status: NEW → ASSIGNED
Summary: [Meta] Use Tiers instead of exclusion profiles → Use Tiers instead of exclusion profiles
Comment 9•7 years ago
|
||
Assignee | ||
Comment 10•7 years ago
|
||
Comment on attachment 8908265 [details] [review]
[treeherder] mozilla:remove-exclusion-profiles-3 > mozilla:master
Thanks for the previous pass. I believe I addressed your concerns.
Attachment #8908265 -
Flags: review?(emorley)
Comment 11•7 years ago
|
||
Comment on attachment 8908265 [details] [review]
[treeherder] mozilla:remove-exclusion-profiles-3 > mozilla:master
Looks great!
How long should we wait before merging this to stage and then prod?
Attachment #8908265 -
Flags: review?(emorley) → review+
Assignee | ||
Comment 12•7 years ago
|
||
I was thinking soaking PR2 for maybe 1 week. I'm fairly certain we can address any non-hiddenness quickly enough that we won't need to re-enable exclusion profiles, but there's little hurry to remove the tables once they're not in use. After 1 week and nobody is asking for my head, then I'll merge this latest PR. :)
Comment 13•7 years ago
|
||
I've exported the current exclusion profiles in case it's useful to refer back to them in the future (with a bit of editing to remove the chronic thousands of entries for the ~"all" case of the particular platform/...).
Now we have this export (which will help with figuring out why things were hidden/bug numbers etc), perhaps we can land the last PR here sooner than a few week away?
Assignee | ||
Comment 14•7 years ago
|
||
Sure, sounds good to me! Thanks for creating that export. I'll go ahead and merge now. :)
Comment 15•7 years ago
|
||
Commit pushed to master at https://github.com/mozilla/treeherder
https://github.com/mozilla/treeherder/commit/863f772a8b13bfb2039574937c0480b5b00c52d5
Bug 1387640 - Remove Exclusion Profiles models/tables
Removes all the models and tables for the ExclusionProfile and
JobExclusion models and related.
Assignee | ||
Updated•7 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•