#180 Enhancement: Changeset file list in variable

[Anonymous]

Originally created by: nescha

Usage of "Script/Command to call when new revision are detected" can be
improved. Several new variables (like %revision, %url...) can be added.
One of the useful ones would be %files.
Since TortoiseSVN tends to be slow on large projects, and big teams do
commit often, it almost blocks OS during an update. But, if you narrow list
of files that are about to be updated, this process would be much faster.

I created batch file for this purpose:

@cls
@SET workingCopyPath="C:\Projects\Flexiweb\app"
@SET userin="n"
@ECHO.
@ECHO.
@ECHO ----------------------------------------------------------
@ECHO  Do you wish to update your Working Copy app folder [n] ?
@ECHO   === %workingCopyPath% ===
@ECHO ----------------------------------------------------------
@SET /p userin=
@IF %userin% EQU y START TortoiseProc.exe /command:update
/path:%workingCopyPath% /closeonend:0

[Anonymous]

Originally posted by: tortoisesvn

There's a slight problem here:
%revision : what should that be when the check finds out that the HEAD revision is
now at 100, but on the last check it was at 80 ? Should %revision be 100? Or 80?

And with %files: CommitMonitor doesn't know a path to your working copy, so all it
could pass in that variable would be relative paths, relative to the repository root.

Labels: -Type-Defect Type-Enhancement

[Anonymous]

Originally posted by: nescha

Since "TortoiseProc.exe /command:update" doesn't accept list of files, but just list
of folders, variable "%folders" would be more appropriate.

List of folders should respect folder hierarchy, meaning that there is no need for
"/app/webroot/img" in list if "/app/webroot" is already present. This isn't
obligatory though cause it can be excluded externally.

[Anonymous]

Originally posted by: nescha

I could use %revision number inside batch file, but I decided not to, since our team
is rather small (4 people) and we always want to have latest revision.

Regarding relative paths, I don't really mind, since they can be externally adjusted.

[Anonymous]

Originally posted by: nescha

I see that you are also involved in development of Tortoise (though here isn't
appropriate place for question about it).
Our project is rather large (300 MB with bunch of small files). Updating of root
folder (even though one file is about to be updated) can take like 2-3 minutes, with
great processor usage. I do have some more repositories that are tracked with
Tortoise, and I turned off "Icon Overlays" (Exclude paths: C:\* - single partition),
and I've set "Status cache" to "None", but still nothing.
Give me some hint, plz.

[Anonymous]

Originally posted by: tortoisesvn

TortoiseProc /update:
does accept a list of files. But if you're using an older version, you have to
specify /notempfile too to make this work.

As for the long time to update, see this thread:
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2376534

[Anonymous]

Originally posted by: nescha

Is there any progress regarding this request? I saw your source code and I feel I can
change it myself pretty easily, but I don't won't to create branch out of your
deployment line cause I do update regularly to latest CommitMonitor revisions. Since
it can be implemented pretty fast and easy, I would appreciate if you could set
higher priority on this one and implement it within next public version/revision.

[Anonymous]

Originally posted by: tortoisesvn

If you think you can do it, please do!
Just attach the patch to this issue once you're done and I'll commit it.

[Anonymous]

Originally posted by: nescha

Huh, though I have good will and enthusiasm, unfortunately, time is variable that
makes me a problem of doing this :(