<br><tt><font size=2>cruisecontrolrb-users-bounces@rubyforge.org wrote
on 04/12/2007 03:58:25 AM:<br>
> I have tried to look for some configuration possibility to make my
<br>
> current scenario work. But I have not found out how to do.<br>
</font></tt>
<br><tt><font size=2>That's exactly where build chaining (discussed in
yesterday "Plans for version 1.2" post) comes handy.</font></tt>
<br><tt><font size=2>In the absense of it, you can actually hack something
together, as follows:</font></tt>
<br>
<br><tt><font size=2>1. Set a project for each of the three modules.</font></tt>
<br><tt><font size=2>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.</font></tt>
<br><tt><font size=2>3. In each of the module builds make "touch [cruise]/projects/sandbox/build_requested"
the last step.</font></tt>
<br>
<br><tt><font size=2>--</font></tt>
<br><tt><font size=2>Alex</font></tt>