[Carbon-dev] Why was the build broken most of the time in the past 3 weeks?
senaka at wso2.com
Fri Feb 4 22:11:06 PST 2011
On Sat, Feb 5, 2011 at 10:08 AM, Amila Maha Arachchi <amilam at wso2.com>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.
> On Sat, Feb 5, 2011 at 7:42 AM, Afkham Azeez <azeez at wso2.com> wrote:
>> 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: **azeez at wso2.com* <azeez at wso2.com>* 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
>> Carbon-dev at wso2.org
> Carbon-dev mailing list
> Carbon-dev at wso2.org
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
*Lean . Enterprise . Middleware
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Carbon-dev