www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Phillips (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-7213) Allow 4 non-ASF email addresses to send to notifications@jclouds.apache.org
Date Sat, 25 Jan 2014 19:42:38 GMT

    [ https://issues.apache.org/jira/browse/INFRA-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882010#comment-13882010
] 

Andrew Phillips commented on INFRA-7213:
----------------------------------------

[~ipv6guru]: If there's anything you need from jclouds to help this along, please let us know!

> Allow 4 non-ASF email addresses to send to notifications@jclouds.apache.org
> ---------------------------------------------------------------------------
>
>                 Key: INFRA-7213
>                 URL: https://issues.apache.org/jira/browse/INFRA-7213
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: Mailing Lists
>            Reporter: Andrew Phillips
>            Assignee: Gavin
>
> At jclouds, we are trying to reduce the "notification noise" on the dev list [1] by moving
builder and pull request review commit notifications to notifications@ (created in INFRA-7180).
> Specifically, we would need these four non-ASF addresses to be able to post to the list:
> - 'buildhive-github@cloudbees.com' (BuildHive)
> - 'jenkins-no-reply@cloudbees.com' (DEV@cloud)
> - 'notifications@github.com' and 'noreply@github.com' (GitHub)
> As per discussion with gmcdonald on IRC, creating a ticket to discuss this.
> [1] http://markmail.org/thread/56h7ranonrfqlukr



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message