You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Erik de Bruin <er...@ixsoftware.nl> on 2013/06/28 09:32:16 UTC
Mustella VM emails to 'issues'?
Hi,
I was just wondering: would it be better if I have Jenkins send the
Mustella run emails to 'issues@'?
The way it stands now, all three runs (main, AIR and mobile) have
tests failing (even after -failures). This means that per full run,
three emails will be sent... twice a day. That will put even Justin's
JIRA email production to shame ;-) I think it will be cleaner if I
direct those emails somewhere they don't interfere with the 'regular'
discussions?
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: Mustella VM emails to 'issues'?
Posted by Erik de Bruin <er...@ixsoftware.nl>.
And just to correct a minor issue with Om's statement: I sure he meant
Jenkins, not JIRA :-)
EdB
On Saturday, June 29, 2013, OmPrakash Muppirala wrote:
> On Fri, Jun 28, 2013 at 12:55 AM, Justin Mclean <justin@classsoftware.com<javascript:;>
> >wrote:
>
> > Hi,
> >
> > > I was just wondering: would it be better if I have Jenkins send the
> > > Mustella run emails to 'issues@'?
> > +0 from me. Someone may break the build and not be aware of it, but if
> > others think that's OK go ahead, I guess someone could politely point it
> > out and suggest they subscribe to issues@ when it occurs.
> >
> >
> Just to assuage this concern, we have already configured JIRA to send
> separate emails to the individuals who broke the build, in addition to
> mailing the list.
>
> Thanks,
> Om
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: Mustella VM emails to 'issues'?
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Fri, Jun 28, 2013 at 12:55 AM, Justin Mclean <ju...@classsoftware.com>wrote:
> Hi,
>
> > I was just wondering: would it be better if I have Jenkins send the
> > Mustella run emails to 'issues@'?
> +0 from me. Someone may break the build and not be aware of it, but if
> others think that's OK go ahead, I guess someone could politely point it
> out and suggest they subscribe to issues@ when it occurs.
>
>
Just to assuage this concern, we have already configured JIRA to send
separate emails to the individuals who broke the build, in addition to
mailing the list.
Thanks,
Om
Re: Mustella VM emails to 'issues'?
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> I was just wondering: would it be better if I have Jenkins send the
> Mustella run emails to 'issues@'?
+0 from me. Someone may break the build and not be aware of it, but if others think that's OK go ahead, I guess someone could politely point it out and suggest they subscribe to issues@ when it occurs.
> That will put even Justin's JIRA email production to shame ;-)
Not sure about that - at last count I had generated 1133 JIRA emails to the dev list :-)
Thanks,
Justin
Re: Mustella VM emails to 'issues'?
Posted by Erik de Bruin <er...@ixsoftware.nl>.
Ok, I think commits@ is it. Om's argument hits home, builds break
because of commits :-)
If no major objections, I'll implement this the coming week.
EdB
On Sat, Jun 29, 2013 at 9:27 AM, OmPrakash Muppirala
<bi...@gmail.com> wrote:
> I think commits@f.a.o would be the best place. Builds break because of bad
> commits (most of the times)
> Moreover an additional list (ex. builds@f.a.o) would be a bit of an
> overkill.
>
> Thanks,
> Om
>
> On Sat, Jun 29, 2013 at 12:16 AM, Frédéric THOMAS
> <we...@hotmail.com>wrote:
>
>> commits@ or issues@ I would say what is better but what is sure is it
>> pollutes the dev list.
>>
>> Those 2 lists are followed as well by committers or at least PMCs,
>> otherwise what do you thing about another list builds@ ? does it worth ?
>>
>> -Fred
>>
>> -----Message d'origine----- From: Alex Harui
>> Sent: Friday, June 28, 2013 4:35 PM
>> To: dev@flex.apache.org
>> Subject: Re: Mustella VM emails to 'issues'?
>>
>>
>>
>>
>> On 6/28/13 12:32 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>>
>> Hi,
>>>
>>> I was just wondering: would it be better if I have Jenkins send the
>>> Mustella run emails to 'issues@'?
>>>
>> Wouldn't commits@ be better?
>>
>>
>>> The way it stands now, all three runs (main, AIR and mobile) have
>>> tests failing (even after -failures). This means that per full run,
>>> three emails will be sent... twice a day. That will put even Justin's
>>> JIRA email production to shame ;-) I think it will be cleaner if I
>>> direct those emails somewhere they don't interfere with the 'regular'
>>> discussions?
>>>
>>
>> I'll try to spend some time cleaning up the runs next week.
>>
>>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: Mustella VM emails to 'issues'?
Posted by OmPrakash Muppirala <bi...@gmail.com>.
I think commits@f.a.o would be the best place. Builds break because of bad
commits (most of the times)
Moreover an additional list (ex. builds@f.a.o) would be a bit of an
overkill.
Thanks,
Om
On Sat, Jun 29, 2013 at 12:16 AM, Frédéric THOMAS
<we...@hotmail.com>wrote:
> commits@ or issues@ I would say what is better but what is sure is it
> pollutes the dev list.
>
> Those 2 lists are followed as well by committers or at least PMCs,
> otherwise what do you thing about another list builds@ ? does it worth ?
>
> -Fred
>
> -----Message d'origine----- From: Alex Harui
> Sent: Friday, June 28, 2013 4:35 PM
> To: dev@flex.apache.org
> Subject: Re: Mustella VM emails to 'issues'?
>
>
>
>
> On 6/28/13 12:32 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>
> Hi,
>>
>> I was just wondering: would it be better if I have Jenkins send the
>> Mustella run emails to 'issues@'?
>>
> Wouldn't commits@ be better?
>
>
>> The way it stands now, all three runs (main, AIR and mobile) have
>> tests failing (even after -failures). This means that per full run,
>> three emails will be sent... twice a day. That will put even Justin's
>> JIRA email production to shame ;-) I think it will be cleaner if I
>> direct those emails somewhere they don't interfere with the 'regular'
>> discussions?
>>
>
> I'll try to spend some time cleaning up the runs next week.
>
>
Re: Mustella VM emails to 'issues'?
Posted by Frédéric THOMAS <we...@hotmail.com>.
commits@ or issues@ I would say what is better but what is sure is it
pollutes the dev list.
Those 2 lists are followed as well by committers or at least PMCs, otherwise
what do you thing about another list builds@ ? does it worth ?
-Fred
-----Message d'origine-----
From: Alex Harui
Sent: Friday, June 28, 2013 4:35 PM
To: dev@flex.apache.org
Subject: Re: Mustella VM emails to 'issues'?
On 6/28/13 12:32 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>Hi,
>
>I was just wondering: would it be better if I have Jenkins send the
>Mustella run emails to 'issues@'?
Wouldn't commits@ be better?
>
>The way it stands now, all three runs (main, AIR and mobile) have
>tests failing (even after -failures). This means that per full run,
>three emails will be sent... twice a day. That will put even Justin's
>JIRA email production to shame ;-) I think it will be cleaner if I
>direct those emails somewhere they don't interfere with the 'regular'
>discussions?
I'll try to spend some time cleaning up the runs next week.
Re: Mustella VM emails to 'issues'?
Posted by Alex Harui <ah...@adobe.com>.
On 6/28/13 12:32 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>Hi,
>
>I was just wondering: would it be better if I have Jenkins send the
>Mustella run emails to 'issues@'?
Wouldn't commits@ be better?
>
>The way it stands now, all three runs (main, AIR and mobile) have
>tests failing (even after -failures). This means that per full run,
>three emails will be sent... twice a day. That will put even Justin's
>JIRA email production to shame ;-) I think it will be cleaner if I
>direct those emails somewhere they don't interfere with the 'regular'
>discussions?
I'll try to spend some time cleaning up the runs next week.