Group or shared runners should have their own monitoring page
Problem to solve
Using shared runners, either between projects or within a group, can quickly become bothersome if they are responsible to handle the CI of a lot of projects. I believe they should have their own page to monitor their activity.
This page could contain the last running pipelines of all the projects it handles. This page could be accessible only to maintainers.
Further details
When debugging and doing work on the CI, we sometimes have to restart our runners. Due to a lack of information, we might think a runner is stuck while it is just running a CI of some project. And finding this information is hard in the Gitlab CE version. Imagine having to run through all the projects the stuck runner is handling to be sure a restart won't stop a CI run. Having a specific page for it would help in my opinion.
To give you an example, in my work team, we work on C++ projects. We have 3 runners:
- one is responsible to run our main branches CI (master, release, dev and hotfixes)
- one is responsible to run our feature branches CI, debug mode only
- one is responsible to run our feature branches CI, release mode only
They all have 15 independent projects to handle.
gitlab-ce2391246 gitlab-ce2278654 gitlab-ce2975006 gitlab-ce4107714