[gatein-dev] Build Failure !!!

[Dimitri]

The problem here is that the list is moderated. So notification on a  
moderated list is useless.
+1 for a gatein-hudson list or another solution.

Dimitri
-- eXo Platform France

Le 9 oct. 2009 à 09:53, Arnaud HERITIER <aheritier at gmail.com> a  
écrit :

> Yes but others will reply that they don't want to be SPAM by those  
> emails and prefer to use hudson/jira dashboards or an RSS feed.
> In my case, I'm like you, you can SPAM me, I'm a master in managing  
> emails in GMails with emails, filters & more.
>
> Cheers,
>
> Arnaud
>
> # Arnaud Héritier
> # Software Factory Manager
> # eXo Platform
> # http://www.exoplatform.com
> # http://blog.aheritier.net
>
>
> On Fri, Oct 9, 2009 at 9:47 AM, Julien Viet <julien at julienviet.com>  
> wrote:
> for me notifications are fine if they can easily filtered by common  
> mail rules.
>
>
> On Fri, Oct 9, 2009 at 9:44 AM, Arnaud HERITIER  
> <aheritier at gmail.com> wrote:
> FYI, in our continuous integration jobs, Maven checks if there are  
> new SNAPSHOTs on our global repository (Nexus - http://repository.exoplatform.org 
> ) for each build.
> Actually our central repository checks if there are new SNAPSHOTs on jboss.org 
>  every 5 minutes.
> Thus if there are less than 5 minutes between the deployment of  
> SNAPSHOTs and the build, it will fail.
> This won't occur anymore when all GateIn resources (jobs,  
> repositories, ..) will be hosted on jboss.org
>
> About notifications, it is very very difficult to have all a team  
> agreed on it. That's why we often push them (issues, continuous  
> integration,..) on a dedicated mailing list (notifications@ maven.apache.org 
>  for exemple). Thus, those who prefer to use RSS feeds for exemple  
> to retrieve those notifications can use it and not subscribe to the  
> mailing list.
>
> Cheers,
>
> Arnaud
>
> # Arnaud Héritier
> # Software Factory Manager
> # eXo Platform
> # http://www.exoplatform.com
> # http://blog.aheritier.net
>
>
> On Fri, Oct 9, 2009 at 2:32 AM, Dimitri BAELI <dbaeli at gmail.com>  
> wrote:
> Hello,
>
>    Last commit broke the build. And will probably block the night  
> team in VN :-)
>
> http://builder.exoplatform.org/hudson/view/All/job/gatein-portal-trunk/97/console
>
> /home/hudson/hudson/jobs/gatein-portal-trunk/workspace/gatein/portal/ 
> trunk/component/pc/src/main/java/org/exoplatform/portal/pc/ 
> ExoKernelIntegration.java:[133,61] cannot find symbol
> symbol  : variable LOCAL_PORTLET_INVOKER_ID
>
>
>
>
>
>
>
> location: interface org.gatein.pc.api.PortletInvoker
>
> Questions:
>    How should we behave in such case ?
>    Can we rollback the commit if the responsible is not present for  
> few hours ? Or let it be and update to the last known stable state.
>
> Experimentation:
>    I'll send the build notifications (only failures and back to  
> normal state) to the gatein-dev list. Tell me if that's not  
> acceptable also.
>    Is there another target ML for that ?
>
> The notification rules:
> Every failed build triggers a new e-mail.
> A successful build after a failed (or unstable) build triggers a new  
> e-mail, indicating that a crisis is over.
> An unstable build after a successful build triggers a new e-mail,  
> indicating that there's a regression.
> Unless configured, every unstable build triggers a new e-mail,  
> indicating that regression is still there.
>
>
> Dimitri BAELI - eXo Platform SAS
>
> _______________________________________________
> gatein-dev mailing list
> gatein-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/gatein-dev
>
>
>
> _______________________________________________
> gatein-dev mailing list
> gatein-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/gatein-dev
>
>
>
> _______________________________________________
> gatein-dev mailing list
> gatein-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/gatein-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/gatein-dev/attachments/20091009/35fbb85e/attachment.html