Add a page showing all packages for a maintainer

[ocharles]

I am a maintainer for a selection of Perl and Haskell packages. I would like to know the status of these packages - whether or not they are building. At the moment I have to work hard to keep emails around indicating when a build succeeds or fails, which is very error-prone. I would like a page that shows all packages I am listed as a maintainer for.

[edolstra]

Yes, this is on my todo list. Hydra since last week or so has a per-user "dashboard" page. The idea is to add a tab that shows all current builds of which the user is a maintainer.

[domenkozar]

Here it is (in my case): http://hydra.nixos.org/user/domen@dev.si/dashboard#tabs-my-jobs

It would be nice to not have to sign in to see that.

[vcunat]

The "my jobs" tab might be nice, but on hydra.nixos.org for me it shows lots of old jobs from uninteresting jobsets and there's no recent job at all. Maybe it's just due to limiting the number of lines, but the tab doesn't seem useful to me as it is.

Fortunately the "Starred jobs" can be used as a substitute; it would actually be great only if there was a way to choose a set of jobsets and automatically star all maintained packages...

[jonringer]

Bump, as this came up again: https://discourse.nixos.org/t/21-05-retrospective/13426/8

Specifically for ZHF, it would be nice for people who have listed themselves as maintainers to see a concise view of builds that they should be aware of.

Also, this would be helpful with staging-next stabilizaiton.

[primeos]

IIRC @Ma27's PR should implement this / fix this issue: #743

Unfortunately Hydra seems to lack maintainers to review and merge PRs... :o

[Ma27]

This PR needs a rebase, other than that I doubt that we'll get this ready for 21.11 considering that this requires a fairly big database migration (and the database of hydra.nixos.org is especially big, so we shouldn't tamper with it before one of the two times in a year, where the usage of Hydra's frontend spikes).

The thing is, I fully understand that it's quite a big amount of work to review... so I'm not sure how to proceed here after a rebase :)