Allow email notifications on builds I'm the author of
under review
Patrick Gibson
Adding support to this much needed distinction. I've had to disable this feature because the signal to noise ratio is too low. I don't want notifications for
main
/ master
branch failures that don't concern me.
Oran Wilder
Merged in a post:
Notifications set to my builds should not trigger on branches you have committed to it should only be the builds you push
O
Oliver Leo Balfour
The "my builds" setting should not include other people's builds on the non default branch.
In my team's setup, we've got a test suite running on the main branch after merges, and some of these tests are broken.
I currently get emails every time someone else pushes to master about the test failures.
I only want notifications about my builds or other people's builds on non-main branches I've pushed to.
Oran Wilder
Updated "my branch" settings are now being tested with Gitlab projects. Will update again as we continue to consider updates for GitHub and BitBucket.
Ambrose Little
Current feature has this for "My Builds," which I found incredibly misleading--if one doesn't read the "fine print":
'My builds
Send me an email every time a build I've pushed fails, and when it’s fixed. Additionally, for Github and Bitbucket projects, include anyone's builds in branches I've pushed to before.'
This isn't "my builds" then. I really don't need to know when my colleagues pushes to a branch that I happen to have pushed before and they break it.
I don't see an option for actually, no, just _MY_ builds. That's what I'm looking for. I guess I'll have to see about filtering on my email client instead. /sigh
Oran Wilder
Merged in a post:
Get notification only for failed builds caused by your commits to git
A
Aamir Afridi
At the moment you can either get email notification or not or notification for the git branches where you pushed.
I push to production and staging branches regularly. It is useful when I get notification for the builds where I pushed something to git. But I get notification for failed builds when other people push to the same branches. I don't want those notifications.
Way to get notification only for the failed builds caused my commits to git not others.
CCI-I-787
Oran Wilder
Merged in a post:
Disable email build notifications on main branch
Max Horstmann
On the notification settings page, under build notifications, it would be nice if the build notifications setting "My branches" would have an additional checkbox to exclude the repo's main (master) branch.
Build failures on the main branch caused by pushes by other devs typically aren't relevant to me, so those notifications are noise.
Alternatively, add another option "My builds", enabling email notifications across all branches but only for builds I have triggered myself.
Oran Wilder
Merged in a post:
Add a new Email Notification Setting for "Only for commits I pushed"
M
Matt Lubner
Please add a new setting for a user's Email Notifications, to the effect of "Send me a personalized email every time a job fails on a commit I've pushed, and for every failed job thereafter, until the job passes."
This added granularity is desired for the case where a user occasionally works on a project, but does not want to be notified of every failing build.
Also, please fix the notification bug where notifications are sent when a build contains both failing and passing jobs (eg. when jobs are run in parallel)! Notifications for parallel jobs within a workflow should not be sent until after all jobs within that workflow have finished. Otherwise, multiple fixed/broken notifications are sent, which is both overwhelming and unhelpful.
CCI-I-493
Oran Wilder
under review
S
Sam Tuckey
yes please, Also show me email notifications for a project/branch combination that fails