The notifications rules are the following:

Attach build log: ALWAYS

ALWAYS SEND TO:
Recipients - those listed in the recipients list at the project level  (that is 
:  comm...@flex.apache.org jmcl...@apache.org) 
Developers - those who made changes to the code
Requestor - the person who initiated the build, if a person (not SCM polling or 
hook)
Culprits - used in conjunction with Developers, gets the culprits from Jenkins 
itself rather than the changeset.

"flex-sdk-mustella" tests is in failure, so we should know in 8hrs ...

Maurice 

-----Message d'origine-----
De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash 
Muppirala
Envoyé : mardi 3 décembre 2013 21:16
À : dev@flex.apache.org
Objet : Re: Test job - Build # 3 - Successful!

Did you try to break the build and see if sends out an email with the log?
That is the most important part :-)

Thanks!
Om


On Tue, Dec 3, 2013 at 12:12 PM, Maurice Amsellem < 
maurice.amsel...@systar.com> wrote:

> Cool, Om.
> So now we will be able to analyze the full mustella build log without 
> having to connect to the VM (in theory :-) That may be helpful.
>
> Maurice
>
> -----Message d'origine-----
> De : OmPrakash Muppirala [mailto:omup...@gmail.com] Envoyé : mardi 3 
> décembre 2013 21:07 À : dev@flex.apache.org Objet : Re: Test job - 
> Build # 3 - Successful!
>
> Yes, got it.  There was a build.zip attachment with one file called log.
>
> Thanks,
> Om
>
>
> On Tue, Dec 3, 2013 at 12:05 PM, Maurice Amsellem < 
> maurice.amsel...@systar.com> wrote:
>
> > Did you receive build.zip attached with the email ?
> >
> > -----Message d'origine-----
> > De : flex.muste...@gmail.com [mailto:flex.muste...@gmail.com] Envoyé :
> > mardi 3 décembre 2013 21:04 À : comm...@flex.apache.org; 
> > jmcl...@apache.org Objet : Test job - Build # 3 - Successful!
> >
> > Test job - Build # 3 - Successful:
> >
> > Check console output at http://localhost:8080/job/Test%20job/3/ to 
> > view the results.
> >
> > (sent from ext-email)
> >
>

Reply via email to