1262578 - Defining the process for bb->tc job visibility changes

Status: RESOLVED FIXED

(Tree Management Graveyard :: Visibility Requests, defect)

Description

[Selena Deckelmann :selenamarie :selena]

Going forward, we think the best way to do tier changes is probably the following: 

* Intree config: make change to builds to tier 1 (help from releng/tc team) -- at this point, bb build and test jobs will also be tier 1, tc tests will be tier 2
* Intree config: make change to tests to tier 1 (help from engprod/tc team)
* Treeherder config: make change to hide buildbot jobs / move to tier 2 -- what is the best way for sheriffs to handle this?

We're going to be going through this process for a lot of different job types, so we'd like to get a consistent set of steps defined for all of them.

Comment 1

[Joel Maher ( :jmaher ) (UTC -8)]

:kwierso, can you confirm this is what you want or add what we should do differently?  We need full support for the sheriffs on this!

Comment 2

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

That sounds about right to me. TC-based jobs are the best place to put the tier information for TC-based jobs, and will make changes easier as time goes on (the change to tier-1 will ride the trains without having to fiddle a lot with Treeherder job profiles). 

The Treeherder changes for moving buildbot jobs to tier-2 or hidden will be easy since those jobs will theoretically just go away at some point, then it's a simple matter of removing the exclusion profiles once they no longer apply to any currently running jobs in our infra.

Comment 3

[Carsten Book [:Tomcat]]

yeah i agree with wes, maybe we can do the same way we did with b2g and marking as tier 2 with the buildbot jobs. I think tier 2 is maybe a good way to have it as backup and can later hide this jobs

Comment 4

[Carsten Book [:Tomcat]]

(In reply to Carsten Book [:Tomcat] from comment #3)
> yeah i agree with wes, maybe we can do the same way we did with b2g and
> marking as tier 2 with the buildbot jobs. I think tier 2 is maybe a good way
> to have it as backup and can later hide this jobs

cameron: would this be possible to use the same process we used for b2g to mark it as tier 3 ?

Comment 5

[Cameron Dawson [:camd]]

Tomcat:(In reply to Carsten Book [:Tomcat] from comment #4)
> cameron: would this be possible to use the same process we used for b2g to
> mark it as tier 3 ?

Absolutely.  There is already an exclusion profile called "Tier-2"  So just update that to include any job you want to be Tier-2 and you're set.  Though, just a reminder that if that exclusion is ALSO in Tier-3, then the job will end up as Tier-3.  Tier-3 beats Tier-2 if they're both set.