Cruisecontrolrb users - Apr 2007 - 1-1 project-archive mapping?

Hi!

If I have understood things correctly in CC.rb, there is a 1-1 mapping 
between "projects" and Subversion modules. For example the normal way
to
add a project is a command like:

    $ cruise add <name> -u <url>

I''m not sure how to use CC.rb for my situation where I don''t
have such a
direct mapping.

I have several Subversion modules that I need to checkout to a 
sandbox-structure like:

    SOMEDIR/moduleA                # from http://HOST/PATH1/moduleA/trunk
    SOMEDIR/moduleB                # from http://HOST/PATH2/moduleB/trunk
    SOMEDIR/moduleC                # from http://HOST/PATH3/moduleC/trunk

My first thought was to create a special Subversion module "testABC" 
that just contained a "Rakefile" for CC.rb to use, and then the needed
svn:externals to bring in moduleA, moduleB and moduleC as subdirectories.

But I guess that will make it impossible for CC.rb to detect that 
something has happened in the Subversion archive. After initial setup 
the testABC module will never change. The changes will be in moduleA, 
moduleB and moduleC, hidden by the svn:external links.

A build in CC.rb also seem to be identified with the revision number. In 
my scenario I have *three* different Subversion module, each with a 
"latest revision" of its own.

I have tried to look for some configuration possibility to make my 
current scenario work. But I have not found out how to do.

Is it possible? Or is there some other way to accomplish something similar?

/Johan Holmberg

cruisecontrolrb-users-bounces at rubyforge.org wrote on 04/12/2007 03:58:25 
AM:
> I have tried to look for some configuration possibility to make my 
> current scenario work. But I have not found out how to do.
That''s exactly where build chaining (discussed in yesterday "Plans
for
version 1.2" post) comes handy.
In the absense of it, you can actually hack something together, as 
follows:

1. Set a project for each of the three modules.
2. Create a project for the sandbox. Make it watch an SVN path with its 
own build file and cruise_config.rb, even if you have no other sources for 
it.
3. In each of the module builds make "touch 
[cruise]/projects/sandbox/build_requested" the last step.

--
Alex
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070412/c31ed95f/attachment.html