Hi,
On 04.04.2012 20:58, Andrew Rist wrote:
On 4/2/2012 2:07 AM, Oliver-Rainer Wittmann wrote:
Hi
On 02.04.2012 06:38, [email protected] wrote:
The Buildbot has finished a build on builder aoo-win7 while building ASF
Buildbot.
Full details are available at:
http://ci.apache.org/builders/aoo-win7/builds/115
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: The Nightly scheduler named 'aoo-win7' triggered this build
Build Source Stamp: [branch incubator/ooo/trunk] HEAD
Blamelist:
BUILD FAILED: failed shell_4
sincerely,
-The Buildbot
The build broke in module sal, because file 'convertiscii.tab' could not be
found.
This file has been removed a couple of days ago by hdu - 2012-03-28, rev.
1306246.
Thus, a clean build is needed to get the dependencies up to date.
There have been 2 clean builds (one was last night's build) since the sal issue
first occurred.
The problem remains - something else is wrong. This would be good to sort out.
Can someone please trigger a clean build for our Windows buildbot?
done twice.
The bad thing is that in the meantime another build breaker has been introduced.
Thus, the clean build breaks again :-(
Thx in advance.
BTW, as our build system is quite complex and not complete regarding its
dependencies I propose to always perform a clean build on our buildbots.
I am not so sure that the build system is all that complex. There are three main
moving parts here:
* The buildbot infrastructure. This is perhaps the most complex part,
but is mostly handled by Apache Infra (thanks Gavin)
* The 'machine recipe' which can be seen in the JIRAs setting up the
buildbots - base OS + packages/requirements. Not rocket science,
and very repeatable.
* The 'build recipe' which is in the openoffice config for the
buildbots. These break down into get source (svn co), run build,
upload results. The syntax in the bb config is a bit cryptic, but
you can figure it out pretty quick, at which point, there's nothing
to exotic going on.
We have a combination of clean builds (svn clobber) and incremental builds going
on. The clobbered builds just take a long time. I'm not sure that we are really
at a point where we need to do a clean build for every platform, for every
build. It just sucks up bandwidth and resources, and takes longer.
All of this is of course covered by a healthy dose of IMHO.
Oh, I did meant the build system of the build bot.
I meant the Apache OpenOffice build system.
E.g., if there is an incompatible change in module X, then a depending module Y
is typically not build when doing an incremental build.
For me, the build bots are the first step to something like "continuous
integration". Thus, from my point of view we can continue with incremental
builds, but we should act asap, if a build bot does not succeed.
I would like to help here, if possible.
I would like to trigger a clean build as soon as possible, because it is needed
due to the changes which have been made or to trigger another build as soon as
possible after a fix for the build breaker has been made.
Is there an interface which I could use to trigger such builds?
Best regards, Oliver.
