[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Hook script questions

From: Linda Halligan <lhalligan_at_bitpusher.com>
Date: 2006-07-07 01:14:55 CEST



I'm not sure what you mean by client in this context. The tomcat instance is
actually running on the same server and I don't have control of what clients
people will be using to update the repository. And I'm not actually going to
be making changes to the site myself.


I'd rather not use a cron job to check for changes since that will require a
delay from commit to website update, and my spec sheet requires an "instant"
update mechanism. So a post commit script seemed like the right answer.


Thanks for the help.





From: Nico Kadel-Garcia [mailto:nkadel@comcast.net]

Now, now, no sticks on newbies (unless they're into it: I have some SCA
friends). Post-commit is really a server side command: if the clients are
known, you could use an SSH or other remote access tool to push an update to


But instead, if I may suggest, why not have the client simply run a query on
a cron-job basis to see if there have been any changes in that project? Use
"svn info -r HEAD /workingcopy" and parse out it's URI and revision number.
If there is a difference between them, pull the update instead of pushing.
That's how I've done it for a website under subversion.
Received on Fri Jul 7 01:16:47 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.