Autotest versus Cruisecontrol.rb - Which to start with???

Hi,

What should I look into re setting up continuous integration? The two I’ve heard about for Ruby on Rails work area AutoTest and CruiseControl.rb.

Any advice?

Tks

start with autotest, on the grounds that it's really staggeringly simple

  $ sudo gem install ZenTest
  $ cd $YOUR_RAILS_APP_DIR
  $ autotest

-faisal

Faisal - I got the following error? Any ideas?

sudo gem install ZenTest
Password:
Need to update 22 gems from http://gems.rubyforge.org

complete

Install required dependency hoe? [Yn]
Install required dependency rubyforge? [Yn]
Successfully installed ZenTest-3.6.0
Successfully installed hoe-1.2.1
Successfully installed rubyforge-0.4.2
Installing ri documentation for ZenTest-3.6.0…
Installing ri documentation for hoe-1.2.1…
Installing ri documentation for rubyforge-0.4.2…
Installing RDoc documentation for ZenTest-3.6.0…
Installing RDoc documentation for hoe-1.2.1…
.
Installing RDoc documentation for rubyforge-0.4.2…
my-computer:~/source/myapp greg$ autotest
/Applications/Locomotive2/Bundles/standardRailsJan2007.locobundle/i386/lib/ruby/site_ruby/1.8/rubygems.rb:382:in latest_partials': undefined method []’ for nil:NilClass (NoMethodError)

    from /Applications/Locomotive2/Bundles/standardRailsJan2007.locobundle/i386/lib/ruby/site_ruby/1.8/rubygems.rb:379:in `each'
    from /Applications/Locomotive2/Bundles/standardRailsJan2007.locobundle/i386/lib/ruby/site_ruby/1.8/rubygems.rb:379:in `latest_partials'

    from /Applications/Locomotive2/Bundles/standardRailsJan2007.locobundle/i386/lib/ruby/site_ruby/1.8/rubygems.rb:342:in `latest_load_paths'
    from /Applications/Locomotive2/Bundles/standardRailsJan2007.locobundle/i386/lib/ruby/site_ruby/1.8/rubygems.rb:341:in `each'

    from /Applications/Locomotive2/Bundles/standardRailsJan2007.locobundle/i386/lib/ruby/site_ruby/1.8/rubygems.rb:341:in `latest_load_paths'
    from /Applications/Locomotive2/Bundles/standardRailsJan2007.locobundle/i386/lib/ruby/gems/1.8/gems/ZenTest-

3.6.0/lib/autotest.rb:109:in autodiscover' from /Applications/Locomotive2/Bundles/standardRailsJan2007.locobundle/i386/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/bin/autotest:36 from /Applications/Locomotive2/Bundles/standardRailsJan2007.locobundle/i386/bin/autotest:16:in load’

    from /Applications/Locomotive2/Bundles/standardRailsJan2007.locobundle/i386/bin/autotest:16

my-computer:~/source/myapp greg$
my-computer:~/source/myapp greg$ echo $PATH
/Applications/Locomotive2/Bundles/standardRailsJan2007.locobundle/i386/bin:/Applications/Locomotive2/Bundles/standardRailsJan2007.locobundle/i386/sbin:/Users/greg/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:

my-computer:~/source/myapp greg$
my-computer:~/source/myapp greg$
my-computer:~/source/myapp greg$

Depends on what you mean by "continuous integration".

If you are a strictly one man orchestra autotest is probably all you
need. It basically runs unit tests whenever you edit a file.

If you have a team and want something to run tests against Subversion
repository, notifying the entire team when someone breaks the build,
that's a job for CC.rb.

Many people, myself included, actually use both.