On 23.04.2010 00:06, Hyrum K. Wright wrote:
> With the increased integration of build tools and other notification
> systems which desire knowledge of commit activity, it would be useful
> to provide an easier mechanism of installing post-commit notification,
> without having to use the hook infrastructure.
I have a slightly different suggestion (but it's in roughly the same area):
Special, or Custom, commands
I was thinking about ReviewBoard and how to make automatic reviews of svn diffs. I have seen people create pre-commit hooks that would run the necessary review script if a certain log comment was specified and then "fail" in the commit, which is one way to do it, and others where the review was posted *every time* code was committed. However, I thought wouldn’t it be very nice to be able to create new client commands that call server hooks directly (ie without having to bodge the required features into an existing hook).
So imagine if I (as a server admin, of course) could configure a new command ("svn review" or "svn special-cmd review") that uses the same mechanism as pre-commit, and calls the server hook "special-review.pl". That's 3 data items in server and client configuration - ('review', 'pre-commit', 'special-review.pl').
Obviously there would be some limitations to this - the data that is sent would have to be the same as the existing hooks, but if I could add a line of config to the client to do this, that would be a rather cool feature to subversion.
This would help with the features requested by this thread - eg, if you want to update your web server, you'd run a new command 'deploy to web', etc. The benefit to this is mainly that you might not want your web server updated all the time with the code you've just committed - especially if you like to checkin partially-developed code. (eg when you go away for the weekend and are worried you might lose your laptop, or your PC dies).
Anyway, that's just an idea for the roadmap :)
Received on 2010-04-23 14:53:08 CEST