errose28 commented on PR #10238: URL: https://github.com/apache/ozone/pull/10238#issuecomment-4594212758
That works too. My high level goal was to create some sort of channel that people could subscribe to for email notifications when there are failures on the master branch. Github currently doesn't support notifications for build failures on a per-branch basis. Moving the build results repo to an apache hosted location would also allow devs to enable notifications for pushes to that repo, which should only happen on master build failures. Another option could be an automated email to the `issues@` mailing list for failures instead of creating a discussion, which users can subscribe to with the standard ASF process. A workaround in the mean time is that devs can individually sign up for CI notifications for the repo and set up email filters on their end for the branches they care about. I'd rather have a one-click solution upstream though. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
