You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Volkan Yazıcı <vo...@yazi.ci> on 2022/03/27 20:41:02 UTC

Fwd: [NOTICE] Introducing GitHub Actions build status notification for git repositories.

In a nutshell, we can configure `.asf.yaml` to email build status. I want
to enable this feature on both `release-2.x` and `master` and point it to `
notifications@logging.apache.org`. Objections?

---------- Forwarded message ---------
From: Daniel Gruno <hu...@apache.org>
Date: Sat, Mar 26, 2022 at 9:58 PM
Subject: [NOTICE] Introducing GitHub Actions build status notification for
git repositories.
To: <an...@infra.apache.org>


Dear Apache projects,
We are happy to announce yet another feature in our beloved .asf.yaml
file, namely GitHub Actions build status emails. As the name suggests,
these are emails that notify of either a failed build using GitHub
Actions, or a change from failure in previous builds to a successful
build. Continuously successful builds will not trigger emails, as that
could be rather spammy.

If your project uses GitHub Actions and wishes to enable status
notification emails, please see our documentation on this at:
https://s.apache.org/asfyaml-gha

In short, what you need to do is add a 'jobs' directive to your existing
notifications section in .asf.yaml if you have such a file (or create it
if you want this feature), for example:

notifications:
   jobs:  dev@foobar.apache.org

We hope this feature will help our projects, and look forward to any
feedback you may have, at: users@infra.apache.org

With regards,
Daniel on behalf of the ASF Infra Team.


PS: Do note that this does not apply to subversion mirrors on GitHub,
notifications@logging.apache.org
as .asf.yaml is not enabled for these repositories.

Re: [NOTICE] Introducing GitHub Actions build status notification for git repositories.

Posted by Matt Sicker <bo...@gmail.com>.
I think it’s a good idea. We used to get notifications of Jenkins build failures, so this would be a great substitute for that.
—
Matt Sicker

> On Mar 27, 2022, at 15:41, Volkan Yazıcı <vo...@yazi.ci> wrote:
> 
> In a nutshell, we can configure `.asf.yaml` to email build status. I want
> to enable this feature on both `release-2.x` and `master` and point it to `
> notifications@logging.apache.org <ma...@logging.apache.org>`. Objections?
> 
> ---------- Forwarded message ---------
> From: Daniel Gruno <humbedooh@apache.org <ma...@apache.org>>
> Date: Sat, Mar 26, 2022 at 9:58 PM
> Subject: [NOTICE] Introducing GitHub Actions build status notification for
> git repositories.
> To: <announce@infra.apache.org <ma...@infra.apache.org>>
> 
> 
> Dear Apache projects,
> We are happy to announce yet another feature in our beloved .asf.yaml
> file, namely GitHub Actions build status emails. As the name suggests,
> these are emails that notify of either a failed build using GitHub
> Actions, or a change from failure in previous builds to a successful
> build. Continuously successful builds will not trigger emails, as that
> could be rather spammy.
> 
> If your project uses GitHub Actions and wishes to enable status
> notification emails, please see our documentation on this at:
> https://s.apache.org/asfyaml-gha
> 
> In short, what you need to do is add a 'jobs' directive to your existing
> notifications section in .asf.yaml if you have such a file (or create it
> if you want this feature), for example:
> 
> notifications:
> jobs: dev@foobar.apache.org
> 
> We hope this feature will help our projects, and look forward to any
> feedback you may have, at: users@infra.apache.org
> 
> With regards,
> Daniel on behalf of the ASF Infra Team.
> 
> 
> PS: Do note that this does not apply to subversion mirrors on GitHub,
> notifications@logging.apache.org <ma...@logging.apache.org>
> as .asf.yaml is not enabled for these repositories.