Issue metadata
Sign in to add a comment
|
figure out if (and how) we should split up tryserver.chromium.linux |
||||||||||||||||||||||
Issue descriptionSplitting this off from bug 669297 ... It's been suggested that we're simply overloaded by having too many builders on tryserver.chromium.linux, and maybe we should split it up. I don't necessarily believe this, and have filed a number of other bugs that I'd like to investigate first, but it might be prudent to figure out what all we need to do if we really do need to split things up. The tasks, I'd guess, are roughly: 1) figure out some division of builders. 2) set up slaves and builders onto a new master. 3) update infra/config/cq.cfg in chromium src.git to reflect the new split. 4) update all of the port forwarding logic, etc. for the new master. Let's figure out how much of this we can do ahead of time so that if we really do need to split things, we can do it fairly quickly and easily. Assigning to dnj@ for now as current MTV trooper, but feel free to find someone else who can take this on. This is lower priority than your other trooper-related tasks.
,
Dec 12 2016
Also, it might be worth considering wether we still want this bot on the cq: https://build.chromium.org/p/tryserver.chromium.linux/builders/blimp_linux_dbg
,
Dec 12 2016
@bpastene - I took blimp_linux_dbg out of the CQ last week, it's just an optional tryserver now.
,
Dec 12 2016
CrOS builders are very low-impact compared to some of the other builders. The varible ones may be significant.
,
Jan 16 2017
I don't think this is urgent any more, so dropping to P2.
,
Jan 16 2017
Also, clearing the owner since I don't think dnj@ is actively working on this, and marking this as *not* blocking 669297.
,
Jan 16 2017
,
Feb 21 2017
Assigning to dpranke as per meeting last week.
,
Feb 21 2017
,
Feb 21 2017
,
Feb 25 2017
,
Feb 25 2017
,
Apr 27 2017
Things seem fairly stable these days, so I think this is a lower priority.
,
Jul 11 2017
famous last words ...
,
Jul 11 2017
,
Jul 12 2017
Current plan: - move all of the non-memory chromeos bots onto a new master.tryserver.chromium.chromiumos I'm pretty sure that this will be good enough to tide us over to LUCI. If not, though, we should next: - move all of the memory bots onto a tryserver.chromium.memory - move all of the fyi bots onto a new tryserver.chromium.fyi - move the "clobber" bots onto a new tryserver.chromium
,
Jul 12 2017
I'm going to mark this as closed since I'm currently working on the plan as per #16. Actually getting the new tryserver up is bug 741164 . We can reopen this if we decide we need additional work. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dpranke@chromium.org
, Dec 12 2016