Repository navigation
Better organization and customized notifications #16
Description
Activity
Both ideas make sense to me. What do you think about grouping pipelines in submenus, i.e. have a top-level entry for the group and then show the pipelines in the submenu?
There's one feature in CCMenu at the moment to deal with large number of pipelines, in the Appearance settings you can tick "only when last build was not successful". That effectively hides all pipelines that are green. The menu will then only display pipelines that are building or where the build is broken.
the functionality ‘only when last build was not successful’ is great. In my specific case, however, I end up with pipelines that do not fail but go very long due to external factors, these I would ‘lose’.
Grouping can be a nice feature, which those who are comfortable with it can manage, those who prefer to have it as it is now can continue to keep it that way.
Tags can be convenient for visibility: you can only define the tag or tags you want to monitor "full visually", and the others you only see if they fail.
The most critical part is the notifications part, that with tags you can only configure the notifications the tags you want.
A kind of matrix
NOTIFICATION BUILD STARTED SUCCESS BROKEN FIXED STILL BROKEN TAG 1 [x] [ ] [ ] [ ] [ ] TAG 2 [x] [x] [x] [x] [x] TAG 3 [ ] [ ] [ ] [ ] [ ]
Hi, thanks for the great tool that I use with satisfaction every day.
I come to propose a couple of ideas that I think can only improve the user experience, tell me what you think.
Most important then for me:
Thanks