Rational ClearQuest for bugs! 

And it's a microsoft (mainly) shop here, so looking forward to modifying
source code or creating new nant tasks developers would be more
comfortable with CCNET.

Also the publishing and CCTray that come with CCNET are VERY nice!

Luntbuild looks very good though! I'll have a look into using that. ( :


Gem

-----Original Message-----
From: Jason Rohwedder [mailto:jro / codegrinder.com] 
Sent: 26 October 2006 16:10
To: ruby-talk ML
Subject: Re: Ruby and Continuous Integration

               *** WARNING ***

This mail has originated outside your organization, either from an
external partner or the Global Internet. 
     Keep this in mind if you answer this message. 


If you're already using Trac to manage bugs and whatnot.. bitten is
pretty neat.. it's written in python, but it can run pretty much
anything.  I haven't used it with rake yet, but I assume it could run
that as easily as a shell script.  It's simple and does what I need for
the time being.
http://bitten.cmlenz.net/

Also, Luntbuild is rather configureable and can deal with many builds
and dependancies well.  It's another java CI tool though.
http://luntbuild.javaforge.com/

-jro

On Oct 26, 2006, at 9:37 AM, Cameron, Gemma (UK) wrote:

>
> Now I've read a couple of old posts about this and the usual response 
> is "use Damage Control" but from the looks of it this hasn't been 
> supported for quite a while...
>
> I'm just curious to see if anyone has used Ruby or Rake to build their

> project and used CruiseControl or CruiseControl.NET to run it. I know 
> it's possible, it would simply need a [N]Ant script with an <exec> 
> task.
> However this will not report the results back for publishing as 
> cleanly or nicely as a nant task, or would it?
>
> Do I need to re-write my rake file in nant?!
>
> Again I'm just curious to find out if anyone is using Rake or Ruby 
> with CruiseControl.NET
>
> Gem
>
> ********************************************************************
> This email and any attachments are confidential to the intended 
> recipient and may also be privileged. If you are not the intended 
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or 
> distribute its contents to any other person.
> ********************************************************************