[DISCUSS] Pre-commit build emails to dev@

[Hitesh Shah <hi...@apache.org>]

Hi folks, 

I am guessing most of you have noticed the high traffic of mails from Apache Jenkins recently. Any complaints/concerns on sending the test-patch pre-commit build emails to dev@tez? Would folks prefer these emails go to issues@ and reduce the traffic on dev@? 

thanks
— Hitesh

Re: [DISCUSS] Pre-commit build emails to dev@

[Hitesh Shah <hi...@apache.org>]

Thanks for your opinions folks. Will redirect these emails to issues@ for the short term. 

@sseth, your comment makes sense. However, I think this might hide any problems in the jenkins jobs themselves in certain failure scenarios.
A better option might be to report general problems in the test patch build system to dev@ and only have the jira comments be updated. i.e. if the job runs fine and adds its comment to jira, no build related email should be generated. Will file a separate jira for this. 

— Hitesh

On Jan 16, 2015, at 12:53 PM, Gunther Hagleitner <gh...@hortonworks.com> wrote:

> +1 Moving to issues@ means less noise on dev.
> 
> On Fri, Jan 16, 2015 at 12:42 PM, Jonathan Eagles <je...@gmail.com> wrote:
> 
>> +1. This allows for filtering in email client as well.
>> On Jan 16, 2015 2:05 PM, "Siddharth Seth" <ss...@apache.org> wrote:
>> 
>>> +1 for moving them over to issues@, or completely getting rid of them -
>>> since the results are posted on jiras in any case, and that would end up
>>> sending out a mail.
>>> 
>>> Thanks
>>> - Sid
>>> 
>>> On Thu, Jan 15, 2015 at 3:24 PM, Hitesh Shah <hi...@apache.org> wrote:
>>> 
>>>> Hi folks,
>>>> 
>>>> I am guessing most of you have noticed the high traffic of mails from
>>>> Apache Jenkins recently. Any complaints/concerns on sending the
>>> test-patch
>>>> pre-commit build emails to dev@tez? Would folks prefer these emails go
>>> to
>>>> issues@ and reduce the traffic on dev@?
>>>> 
>>>> thanks
>>>> — Hitesh
>>>> 
>>>> 
>>>> 
>>> 
>> 
> 
> -- 
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to 
> which it is addressed and may contain information that is confidential, 
> privileged and exempt from disclosure under applicable law. If the reader 
> of this message is not the intended recipient, you are hereby notified that 
> any printing, copying, dissemination, distribution, disclosure or 
> forwarding of this communication is strictly prohibited. If you have 
> received this communication in error, please contact the sender immediately 
> and delete it from your system. Thank You.

Re: [DISCUSS] Pre-commit build emails to dev@

[Gunther Hagleitner <gh...@hortonworks.com>]

+1 Moving to issues@ means less noise on dev.

On Fri, Jan 16, 2015 at 12:42 PM, Jonathan Eagles <je...@gmail.com> wrote:

> +1. This allows for filtering in email client as well.
> On Jan 16, 2015 2:05 PM, "Siddharth Seth" <ss...@apache.org> wrote:
>
> > +1 for moving them over to issues@, or completely getting rid of them -
> > since the results are posted on jiras in any case, and that would end up
> > sending out a mail.
> >
> > Thanks
> > - Sid
> >
> > On Thu, Jan 15, 2015 at 3:24 PM, Hitesh Shah <hi...@apache.org> wrote:
> >
> > > Hi folks,
> > >
> > > I am guessing most of you have noticed the high traffic of mails from
> > > Apache Jenkins recently. Any complaints/concerns on sending the
> > test-patch
> > > pre-commit build emails to dev@tez? Would folks prefer these emails go
> > to
> > > issues@ and reduce the traffic on dev@?
> > >
> > > thanks
> > > — Hitesh
> > >
> > >
> > >
> >
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: [DISCUSS] Pre-commit build emails to dev@

[Jonathan Eagles <je...@gmail.com>]

+1. This allows for filtering in email client as well.
On Jan 16, 2015 2:05 PM, "Siddharth Seth" <ss...@apache.org> wrote:

> +1 for moving them over to issues@, or completely getting rid of them -
> since the results are posted on jiras in any case, and that would end up
> sending out a mail.
>
> Thanks
> - Sid
>
> On Thu, Jan 15, 2015 at 3:24 PM, Hitesh Shah <hi...@apache.org> wrote:
>
> > Hi folks,
> >
> > I am guessing most of you have noticed the high traffic of mails from
> > Apache Jenkins recently. Any complaints/concerns on sending the
> test-patch
> > pre-commit build emails to dev@tez? Would folks prefer these emails go
> to
> > issues@ and reduce the traffic on dev@?
> >
> > thanks
> > — Hitesh
> >
> >
> >
>

Re: [DISCUSS] Pre-commit build emails to dev@

[Siddharth Seth <ss...@apache.org>]

+1 for moving them over to issues@, or completely getting rid of them -
since the results are posted on jiras in any case, and that would end up
sending out a mail.

Thanks
- Sid

On Thu, Jan 15, 2015 at 3:24 PM, Hitesh Shah <hi...@apache.org> wrote:

> Hi folks,
>
> I am guessing most of you have noticed the high traffic of mails from
> Apache Jenkins recently. Any complaints/concerns on sending the test-patch
> pre-commit build emails to dev@tez? Would folks prefer these emails go to
> issues@ and reduce the traffic on dev@?
>
> thanks
> — Hitesh
>
>
>