Better organization and customized notifications

ccmenu / ccmenu2

CCMenu is a Mac app that shows the status of builds on CI/CD servers in the menu bar.

https://ccmenu.org/

Apache License 2.0

61 stars 6 forks source link

Better organization and customized notifications #16

Open bsramin opened 1 month ago

bsramin commented 1 month ago

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.

Give the ability to group or tag pipelines, if I start having dozens of them, it becomes inconvenient to have an endless list
Create a widget with pipelines (with ability to filter only the ones you are interested in)

Most important then for me:

create custom notifications per tag or per single pipeline: I have an estimated 30/35 pipelines of which several start -every minute- however I also have builds on github that I would like to monitor. If I activate build or success events by having notifications every minute I literally get bombarded with notifications and instead miss the important ones of builds that start 1-2 times a day.

Thanks

erikdoe commented 1 month ago

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.

bsramin commented 1 month ago

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	[ ]	[ ]	[ ]	[ ]	[ ]