Re: question about modificatoinset of svn

Your problem is that you have the same RepositoryLocation in the SVN
sub-task of ModificationSet used for both projects. 

Instead of using RepositoryLocation setting in SVN sub-task of
ModificationSet, use LocalWorkingCopy:

<modificationset quietperiod="${quiet.period}">
     <svn LocalWorkingCopy="${project.root}" username="${svn.user}"
password="${svn.password}"/>
</modificationset>

Since LocalWorkingCopy is unique for each project, you will not have
that issue.

John

John Burrows
Release Engineer, SCM
S1 Corporation

>Subject: [Cruisecontrol-user] question about modificatoinset of svn
>	repository
>To: <[email protected]>
>Message-ID: <[email protected]>
>Content-Type: text/plain; charset="iso-8859-1"
>
>Hi,
>
>I am using cruise control 2.8.2. I have the following case which
troubles me. Here is my setup:
>
>I have one svn repository, with trunk and branch 2 projects.
>
>The svn url for trunk is http://svnhost/svnroot/projectA/trunk
>the url for branches is http://svnhost/svnroot/projectA/branches/1.0
>
>In my cruisecontrol control.xml, I have 2 projects:
>
><project name="trunk" buildafterfailed="false">
>...
>        <modificationset quietperiod="${quiet.period}">
>             <svn RepositoryLocation="${svn.portal.project}"
username="${svn.user}" password="${svn.password}"/>
>        </modificationset>
>...
></project>
>
><project name="branch1.0" buildafterfailed="false">
>...
>        <modificationset quietperiod="${quiet.period}">
>             <svn RepositoryLocation="${svn.portal.project}"
username="${svn.user}" password="${svn.password}"/>
>        </modificationset>
>...
></project>
>
>As you can see, both projects pointing to the different URL path of
svn, but they are in the same svn repository.
>
>Here is the problem:
>
>What I want is ONLY build each projects when there is code check-in
into each path. Trunk build should only starts when >there is code
check-in into trunk path; and branch 1.0 build should only starts when
code is checked in into branch 1.0 >path.
>
>But right now, when there is code check in into the trunk, the branches
1.0 will queued and started too after the trunk >build finished; of
course with no real modification showing the final build report. My
guess is that when there is code >check in, even in the trunk path, the
revision number will change in the whole svn repository, make the branch
1.0 >project thinks there is modification.
>
>Does anyone has the similar problem? If so, is there a good solution?
>
>Thanks

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev