Hi All, I'm currently setting-up cruise control 2.2.1 to setup a continious build on the latest SVN source. It will compile XWiki and run tests everytime there are changes in SVN, including the cactus based tests. Results will be published on a web site: http://build.xpertnet.biz and a notification email will be sent either to the dev list or the commit lists. Any comments about the choice: dev or commit list ? I might automatically publish the artifacts to one of the xwiki.com production machines. The build machine is running Mandrake Linux. Ludovic -- Ludovic Dubost XPertNet: http://www.xpertnet.fr/ Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost AIM: nvludo Yahoo: ludovic
-----Original Message----- From: Ludovic Dubost [mailto:[email protected]] Sent: mercredi 20 avril 2005 20:44 To: [email protected] Subject: [xwiki-dev] Cruise Control
Hi All,
I'm currently setting-up cruise control 2.2.1 to setup a continious build on the latest SVN source. It will compile XWiki and run tests everytime there are changes in SVN, including the cactus based tests. Results will be published on a web site: http://build.xpertnet.biz and a notification email will be sent either to the dev list or the commit lists.
Any comments about the choice: dev or commit list ?
I'd say commit list would be the best. This is where we get all the automatic notifications: - SCM commits - xwiki topic change (when this is available) - build failures
I might automatically publish the artifacts to one of the xwiki.com production machines.
The build machine is running Mandrake Linux.
Excellent! Thanks -Vincent
participants (2)
-
Ludovic Dubost -
Vincent Massol