Hi, On Sat, Feb 5, 2011 at 11:41 AM, Senaka Fernando <[email protected]> wrote:
> > > On Sat, Feb 5, 2011 at 10:08 AM, Amila Maha Arachchi <[email protected]>wrote: > >> Hi Azeez, >> >> This was due to two reasons. >> >> 1. There were problems occurring at the time of svn up before a build. >> There were few times where the svn up couldn't complete and build failing >> due to that. It felt like the files were corrupted, so we took a fresh >> checkout. We also fixed some issues in the build script too. >> >> 2. Yes, people being careless when committing. Most frequent mistake I >> have seen is "not committing the complete set of changes". >> > > 3. As I have mentioned, we need to revert back-and-forth for testing since > the latest stable version was built sometime back. So, if the trunk is not > stable and it was not fixed then and there, the chances of instabilities > being introduced through commits done by mistake elevates. One solution is > to hold back until the entire trunk stabilizes, but if we did that, we would > have been waiting for a long time without committing, which would've delayed > releases. So, it is urgent to stabilize the trunk and keep continuous builds > running throughout so that stability is ensured. > > 4. Bad practice for not maintaining changelists for hacks. Actually, I > don't think that most of us have the habit of maintaining a separate > changelist for hacks to avoid them accidentally being committed. > > 5. We can't call this bad, but one reason is that the frequency of > continuous builds have been elevated during the last few days. And, even if > you realized that something was improper and fix that, you'd notice that a > build failure has been triggered by the time the fix was made. But, this > should not be an excuse for not checking whether the "complete set of > changes" are committed for instance. > Yes. Consider this for example. Build fails due to a compilation failure. Folks come to know this via the email. But as soon as the email is triggered, a new build is also triggered. So, by the time the svn up for the new build is completed, fix for the failure might not have been committed. Therefore, there can be two build failures due to a single reason sometimes. Sometimes we kill the build when we realize this and wait till the issue is fixed. But I dont recommend it much. This leads to svn locks, file getting corrupted, do svn cleanups etc. But, if we can halt commits for half a day, I believe we'll be able to get a successful build (manually). Then, there will be packs for QA folks to test. Then we can trigger the continuous build. (There was a problem of ESB packs not being available even after a successful build. I think ESB build is broken. We can fix those issues and make a complete set of packs available) Thanks, AmilaM. > > Thanks, > Senaka. > >> >> Thanks, >> AmilaM. >> >> On Sat, Feb 5, 2011 at 7:42 AM, Afkham Azeez <[email protected]> wrote: >> >>> Guys, >>> I noticed many build failure discussions on carbon-dev in the past 3 >>> weeks? What is the reason for this? Are people being careless when they >>> commit? Do our Maven repos have problems? What happened? >>> >>> -- >>> *Afkham Azeez* >>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com >>> , >>> * >>> * >>> *Member; Apache Software Foundation; >>> **http://www.apache.org/*<http://www.apache.org/> >>> * >>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>> * >>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>> * >>> * >>> *Lean . Enterprise . Middleware* >>> >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> [email protected] >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > *Senaka Fernando* > Product Manager - WSO2 Governance Registry; > Associate Technical Lead; 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 > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
