On Tue, May 24, 2011 at 16:40, 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).
What exactly, is your worry there? Commits are atomic and serial; if 2
people issue an svn commit at the same time, whichever commit reaches
the server will wait in line until the first completes (either by
failing/aborting, or by committing successfully). If both are
committing to the same path, the second will be refused & informed
that he must update his working copy before he may commit.
> 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.
>>Yes, all commands have a (sometimes small) resource demand, andpolling frequently is generally not a good solution.
> Many services (especially bidirectional connections) are constantly polling but my question mainly pertains to if the Update command when there is no update needed consumes too much resources for this to be useful.
Subversion is not designed to be polled in this way. svn update will
utilize minimal server time & resources if there is no change to
retrieve, but that isn't a free license to poll every few seconds.
Subversion's hooks are purpose-built to allow you to do what you're
looking for - trigger an action upon a specific event in the
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-05-25 02:12:39 CEST