I am personally happy with the build process that we right now. Because, it is neither the build process nor the build report that is important - rather keep the build stable.
I think, what we should focus right now and put the effort on is to make sure that the build succeeds every night. Even now, the build has been broken for three straight nights, and at the same place. What use we have with a report then, if the build is broken like this? On Sun, Nov 21, 2010 at 10:22 PM, Senaka Fernando <[email protected]> wrote: > Hi all, > > Just happened to see a nice graphical build report, [1] generated from > Buildbot, [2], and thought whether it would be cool to use this? > > AFAIU, this can be used to track builds triggered off .sh files, [3], like > our Carbon/Stratos build, and it seems to be relatively easy to setup. > Interestingly enough it also has an IRC client, which could notify us on our > IRC channel. You can find some screenshots at [4]. > > So WDYT about $subject? > > [1] http://build.reviewboard.org/waterfall > [2] http://buildbot.net/ > [3] http://buildbot.net/trac/wiki/FAQ > [4] http://buildbot.net/trac/wiki/ScreenShots > > Thanks, > Senaka. > > -- > *Senaka Fernando* > Associate Technical Lead & Product Manager - WSO2 G-Reg; > WSO2, Inc.; http://wso2.com* > Member; Apache Software Foundation; http://apache.org > > E-mail: senaka AT wso2.com > **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 > Linked-In: http://www.linkedin.com/in/senakafernando > > *Lean . Enterprise . Middleware > > Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org
_______________________________________________ Carbon-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
