On May 6, 2009, at 3:09 AM, Johannes Frandsen wrote:
Had a quick glaze at buildbot:
It is of course a pretty compelling reason to choose buildbot over
cruisecontrol based on the notion that buildbot is a part ASF and is
provided as a service for all projects but......
* I dont see anywhere to sign up for this service
* buildbot looks like it still in beta
* buildbots webinterface/frontend seems somewhat plain compared to
cruisecontrol
* buildbot seems overly complex compared to cruisecontrol
(statement based on the documentation)
* I have never heard of buildbot before.....who is using it?
* I heard of many who uses cruisecontrol, heck even pragmatic
programmer books have been written about using it.
* cruisecontrol is also completly free (BSD license)
* cruisecontrol has very good php support through phpundercontrol
....but if we can't have a cruisecontrol hosted anywhere that
doesn't help us and the we "stock" with buildbot anyway.
Anywho.......
I think a buildserver...... in any incarnation....... is better than
no buildserver so whatever we decide on I'll gladly help with the
setup.
Joe
I'm most familiar with the Gump setup at Apache, but I'm guessing the
other continuous integration facilities work in a similar manner. The
Gump meta-data is hosted in the ASF SVN and any committer on any
project can tweak their build definition (but few do). Gump is pretty
much a Ant or shell file driven thing. Gump's reason for being is to
run a nightly build of the open-source Java universe so that breaking
changes in one package are found as soon as possible. Obviously
log4php doesn't have a dependency on the Java software stack, so it
doesn't benefit from early warning on breaking changes.
Continuum (a spin off of the Maven project) would likely be my
choice. log4php has a Maven 2 build (the pom.xml) file for the
primary purpose of keeping the documentation and site updating
strategy consistent with the other Logging Services projects. That
doesn't need to be the projects definitive build script, but it makes
LS site maintenance easier if they are all using the same tools.
mvn test (Mac OS/X) currently fails with the current message:
test:
[exec]
[exec] Warning: require_once(PHPUnit/Util/Filter.php): failed to
open stream: Not a directory in /usr/bin/phpunit on line 40
[exec]
[exec] Fatal error: require_once(): Failed opening required
'PHPUnit/Util/Filter.php' (include_path='.:/usr/share/pear') in /usr/
bin/phpunit on line 40
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] An Ant BuildException has occured: The following error occurred
while executing this line:
/Users/curta/ls-svn/log4php/build.xml:63: exec returned: 255
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 23 seconds
[INFO] Finished at: Wed May 06 22:40:39 CDT 2009
[INFO] Final Memory: 9M/19M
[INFO]
------------------------------------------------------------------------
I don't have my Linux box available at the moment and not sure that
I've ever tried on Mac OS/X.
I can look at this more tomorrow.
