On Fri, Apr 23, 2010 at 06:53, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On 23.04.2010 00:06, Hyrum K. Wright wrote:
>> With the increased integration of build tools and other notification
>> which desire knowledge of commit activity, it would be useful to provide
>> easier mechanism of installing post-commit notification, without having to
>> use the hook infrastructure. Imagine a user being able to set up commit
>> mails, CIA notifications, and buildbot notifications *without* having to
>> have access to the repository. To that end, I propose the following.
>> Simply a versioned property, which, when encountered during the course of
>> commit, causes the server to emit a notification. This property would be
>> list of URLs, to which the repository would send a specially formatted
>> with the information about the commit. (The idea being that a committer
>> the project could set up this property, as well as the server which
>> these notifications, all without the intervention of the repository
>> administrator.) As part of the bubble up, the repo would queue these
>> and then POST to them during the post-commit phase of the commit.
> We have something similar in TortoiseSVN: client-side hook scripts.
> Some people use those to send out notifications after a commit, some to copy
> files to their webserver, ...
> But TortoiseSVN gathers all information purely on the client side. So I'm
> not sure if this feature in svn would require a server-side change or hook
> script to do that?
If the committers use various clients, then yes: some kind of
server-side solution would be needed.
Received on 2010-04-23 13:00:54 CEST