1032220 - Decide whether to switch back to a "single repo per tab" model

Status: RESOLVED FIXED

(Tree Management :: Treeherder, defect, P2)

Description

[Ed Morley [:emorley]]

At the moment, we have quite a few bugs relating to the pinned repos feature.

We always new from the outset that there would be pros/cons to the "single tab for treeherder that handles several repos" model - however I'm wondering if either temporarily (or even permanently), we should switch back to presuming people will use several tabs, one per repo they are interested in (we could still allow people to "favourite" repos, as an improvement to TBPL's MRU tree switcher menu, but just not slow the tab down by loading background state for several repos).

I've marked this bug as blocking several issues which are related to the single vs multi repo per tab model.

My main concern at present, is that performance isn't good enough to switch back and forth between repos (bug 1032216), so I'm going to have to have several app tabs open anyway - at which point the compromises (eg screen estate, the issues Phil mentions in bug 1032013) are being experienced without the advantages.

Comment 1

[Ed Morley [:emorley]]

s/new/knew/ (lol)

Comment 2

[Ed Morley [:emorley]]

Note bug 1031867 is proposing switching from "show unclassified failure counts just for the current view, rather than the last 7 days", which means that for background pinned repos, we don't really have anything to show for the count, adding a plus in the "single repo per tab model" column, I think?

Comment 3

[Cameron Dawson [:camd]]

At this point, it is optional to have watched repos.  By default, you don't.  You can switch to a new repo with the "Repos" panel.  But you watch multiple, if you want.  The count shown next to the watched repo is the unclassified failures in the last 24 hours.  Whereas the count on the yellow button to the right are the unclassified failures on the current page.

Do these changes now make this bug either fixed or obsolete?  Or is it still cumbersome with what's there?  My attempt was to make this the best of both worlds.  The watch multiple provides you the 24 count, plus the tree status on each watched repo.  Hopefully that's valueable?  :)

When Ed gets back, perhaps we can re-evaluate and discuss with Ryan, and Philor.

Comment 4

[Ed Morley [:emorley]]

Yeah things are definitely better now, thank you. I guess let's stick with it and once we get used to the workflow we can close this bug out one way or another. Either way it's not blocking any more I don't think.

Comment 5

[Ed Morley [:emorley]]

(Inverting dependencies so this bug doesn't appear in the blocker bug tree view)

Comment 6

[Ed Morley [:emorley]]

Decision made :-)