Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better organization and customized notifications #16

Open
bsramin opened this issue Sep 18, 2024 · 2 comments
Open

Better organization and customized notifications #16

bsramin opened this issue Sep 18, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@bsramin
Copy link

bsramin commented Sep 18, 2024

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
Copy link
Member

erikdoe commented Sep 26, 2024

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.

@erikdoe erikdoe added the enhancement New feature or request label Sep 26, 2024
@bsramin
Copy link
Author

bsramin commented Sep 26, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

2 participants