Re: <svn> Differences between LocalWorkingCopy and RepositoryLocation

Hi Grégoire

I believe the same action is carried out for both the 
"RepositoryLocation" and "LocalWorkingDirectory", since you can run the 
"svn log" with either a PATH or a URL (run "svn help log" for more details).

I personally prefer the RepositoryLocation option, since this remove the 
requirement of having a checked out module locally - which is needed by 
"LocalWorkingDirectory".  You just have to be careful to provide the 
full path to the module's base directory that you want Cruise Control to 
monitor - so that it doesn't go and check everything else.


For example, we have the following structure in SVN:
- support/
  - trunk
  - branches/
    - branch_X_Y
  - tags/
    - tag_X_Y_Z

For the "trunk" build we have: 
RepositoryLocation="svn+ssh://server/repo/support/trunk"
For the "tag" build we have: 
RepositoryLocation="svn+ssh://server/repo/support/tags/tag_X_Y_Z"

If we were using the "LocalWorkingDirectory", then it would be something 
like:
-> LocalWorkingDirectory="path/to/support-trunk"
where "support-trunk" was created manually using "svn co 
svn+ssh://server/repo/support/trunk support-trunk".


Not sure if that is of any help to you or not, just my own opinion and 
experience on the matter.


Regards,
Nhat Tran

recycling spam wrote:
> 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
> _______________________________________________
> Cruisecontrol-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user
>   

------------------------------------------------------------------------------
Crystal Reports &#45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty&#45;free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects