Bug #10715
Jenkins' default view hides queued test suite runs
100%
Description
On https://jenkins.tails.boum.org/ the “Filtered Build Queue” does not show wrap_test_Tails_ISO_*
jobs, so it’s not very useful and I never use it: I have to use https://jenkins.tails.boum.org/view/Raw/ to get an overview of what our Jenkins setup is up to. I find it strange that I have to use a non-default view to get such basic information.
Subtasks
History
#1 Updated by bertagaz 2015-12-07 02:49:14
- Assignee changed from bertagaz to intrigeri
Hmm, ok. I made it that way thinking that people would probably be happy to have the default view without all this wrap_test_* pending jobs, that are sometimes quite bloating the view given their number. I can still change that if you find it that disturbing.
#2 Updated by intrigeri 2015-12-07 03:09:36
- Assignee changed from intrigeri to bertagaz
> I made it that way thinking that people would probably be happy to have the default view without all this wrap_test_* pending jobs, that are sometimes quite bloating the view
I can totally understand why we might want to trim the display, e.g. buy not listing the details of wrap_test_*
but instead “plus N wrap_test_Tails_ISO_*” and a “show all” button. I don’t understand what value a queue view gives if it pretends the queue is empty (from which I could conclude that my next push will trigger a build + test suite that’ll be done in ~6 hours), while it’s not.
But I can live with using the Raw view myself and won’t argue further.
> given their number.
Thankfully the plan is to fix that :)
#3 Updated by bertagaz 2015-12-07 04:21:11
- Assignee changed from bertagaz to intrigeri
intrigeri wrote:
> > given their number.
>
> Thankfully the plan is to fix that :)
Then we can maybe wait a bit before closing this ticket, and reevaluate when the queue will be shorter?
#4 Updated by intrigeri 2015-12-07 05:33:02
- Assignee changed from intrigeri to bertagaz
> Then we can maybe wait a bit before closing this ticket, and reevaluate when the queue will be shorter?
Whatever you want, I know how to see the info I want from that page, and I don’t need to understand your rationale for hiding it by default.
#5 Updated by bertagaz 2016-01-27 10:49:48
- Target version changed from Tails_2.0 to Tails_2.2
#6 Updated by bertagaz 2016-03-10 18:51:07
- Target version changed from Tails_2.2 to Tails_2.3
#7 Updated by bertagaz 2016-04-22 10:08:22
- Status changed from Confirmed to In Progress
- Assignee changed from bertagaz to intrigeri
- % Done changed from 0 to 80
- QA Check set to Ready for QA
intrigeri wrote:
> Whatever you want, I know how to see the info I want from that page, and I don’t need to understand your rationale for hiding it by default.
Ok, so I’ve set back the default view without any filtering of the queue. I still wonder how other users will perceive the meta jobs in the queue, and how it will blurry a bit more their vision of this tool or not.
#8 Updated by intrigeri 2016-04-25 03:42:55
- Status changed from In Progress to Resolved
- Assignee deleted (
intrigeri) - % Done changed from 80 to 100
- QA Check changed from Ready for QA to Pass
bertagaz wrote:
> Ok, so I’ve set back the default view without any filtering of the queue.
Thanks, resolved then.
#9 Updated by intrigeri 2016-04-25 03:44:14
bertagaz wrote:
> I still wonder how other users will perceive the meta jobs in the queue, and how it will blurry a bit more their vision of this tool or not.
Feel free to try and find a way to hide the noise (which I would welcome) without hiding the relevant info, if you wish :)