Re: [Cruisecontrol-user] Build dependency question.

[Jeffrey F. <jef...@gm...>]

Hi Jason,
you can do what you want but you'll need to make subclasses of the Veto
plugin & the BuildStatus plugin.

For the "AllBuildStatus" plugin I think you could just change a single line
to have all the modifications returned:

                    return name.compareTo(filename) > 0 &&
Log.wasSuccessfulBuild(name);

becomes:

                    return name.compareTo(filename) > 0;

Then with your "OutOfDateVeto" override the getBuildStatus() method to
return an instance of your AllBuildStatus class.

Jtf


On Thu, May 14, 2009 at 8:25 AM, Jason Schadel <ja...@aw...> wrote:

> I have two projects.  I want project_a to be built regardless if
> project_b is passing or failing, as long as project_b is up-to-date.
> Project_b updates code in project_a source so if project_a updates
> before project_b, project_b could miss some modifications.  I tried
> the following configuration, but it seams that project_a gets vetoed
> because of project_b not being successful.
>
> Project_a modificationset:
>       <veto>
>        <triggers>
>          <svn localWorkingCopy="/home/sites/project_a/tests/cases/other" />
>        </triggers>
>        <buildstatus logdir="logs/project_b" />
>       </veto>
>
>       <!-- Build if changes to this project. -->
>       <svn localWorkingCopy="/home/sites/project_a" />
>
> Project_b modificationset:
>       <svn localWorkingCopy="/home/sites/project_b" />
>       <svn localWorkingCopy="/home/sites/project_a/tests/cases/
> other" />
>
> I tried taking <buildstatus> out of the <veto> block but that causes
> an invalid configuration.
>
> Any ideas?
>
> -Jason
>
>
-- 
Build engineer training: http://ci-guys.com