<svn> Differences between LocalWorkingCopy and RepositoryLocation

recycling spam <[email protected]>
Newsgroups gmane.comp.java.cruise-control.user
Message-ID <[email protected]>
Hi,

I'm new to CC and would like to know what are the actual differences
between LocalWorkingCopy and RepositoryLocation.
Our modification set is:
        <modificationset QuietPeriod="60">
            <svn RepositoryLocation="${externals.repository.url}"
Password="${svn.password}" Username="${svn.username}" />
        </modificationset>

The issue I have is that every 5 minutes, CC execute a PROPFIND
operation on each and every files of the repository. I suppose it does
so to detect modifications, by fetching the revision of each file and
compare it with some cached value. I find it a bit odd: in two days,
CC issued about 9 000 000 PROPFIND requests.... It is 57 per seconds,
it will quickly kill my disk.

So I though I would use a LocalWorkingCopy property instead of the
RepositoryLocation in the hope that CC will use the svn log to detect
changes instead of travelling the entire repository.
I've search for explanation of the differences between both properties
but had no luck so far. And CC documentation is quite laconic about
it:
[quote]
LocalWorkingCopy Relative or absolute path to the local working copy
of the Subversion repository of which to find the log history.
RepositoryLocation The url to the Subversion repository on which to
find the log history.
[/quote]

They both mention svn log although I wonder how svn log i used with
the RepositoryLocation.

Best regards,

Grégoire.

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.