Hi Andrew
I know it's somewhat vapour at the moment, and I'm keeping somewhat
quiet, but the new post-Audrey'fied PITA design is aiming at exactly
what you have described.
Initial deployment targets include a pugs smoker, parrot smoker, and
CPAN Testers 2.
Of course, I have no idea how you projects are structured, but it may
well be that it would be appropriate.
Of course, it partly depends on how quickly you need it... if you are in
a hurry, then I'll get back to you in a few months.
Adam K
Andrew Savige wrote:
We are looking at introducing continuous builds/smoke tests at
work across a number of platforms (mainly Windows and Unix),
building a number of different languages (mainly C++).
I quick google uncovered the list below.
Anyone got any advice?
Thanks,
/-\
Perl
----
* AutoBuild: http://www.autobuild.org/,
http://search.cpan.org/dist/Test-AutoBuild/
* http://search.cpan.org/dist/Test-Smoke/
* http://search.cpan.org/dist/Test-Nightly/
Other Open Source
-----------------
* BuildBot (Python): http://buildbot.sourceforge.net/
* DamageControl (Ruby):
http://opensource.thoughtworks.com/projects/damagecontrol.jsp
* CruiseControl (Java): http://cruisecontrol.sourceforge.net/
* CruiseControl.NET:
http://confluence.public.thoughtworks.org/display/CCNET/Welcome+to+CruiseControl.NET
* Eclipse plug-in: http://www.eclipse.org/
* Tinderbox: http://www.mozilla.org/tinderbox.html
* BusyB: http://sourceforge.net/projects/busyb
Commercial
----------
* ParaBuild: http://www.viewtier.com/products/parabuild/index.htm
* BuildForge: http://www.buildforge.com/
Send instant messages to your online friends http://au.messenger.yahoo.com
