On Tue, May 24, 2011 at 4:40 PM, JGalarza <jgalarza_at_astromed.com> wrote:
> I guess a post-commit hook or Push notification could be used to but it's not really what I'm
> looking for. I wanted a way to retrieve just the revision numbers of my current directory and
> the trunk so that I could trigger the update if they are different. I wanted to avoid the issue of
> a user committing a new license and a developer committing a change right during the
> upload/commit (sort of a race condition).
>
> Really I just want a command-line way of determining if the portal's directory needs an update
> or some automated way that will not affect the portal user's process so everything feels
> seamless. Any human interaction once the portal is setup is not really wanted.
There us is always a risk of a race condition no matter how you
trigger the update. Using a
post-commit hook, you can more easily restrict the triggering to only
when files shown on the
web site are committed. (The post-commit hook gets a list of the files
just committed.) Also,
a post-commit hook will only run when a commit is done, while a script
that uses svn info
would have to be run periodically.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2747080
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-05-25 00:19:50 CEST