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

Re: idea of new feature: some way of calling external command after each commit

From: Greg Stein <gstein_at_gmail.com>
Date: Thu, 7 May 2009 03:03:00 +0200

In short... that just won't work.

Every possible committer, no matter the platform, is going to have to
have access to that external program. And if they don't? What then?
How is the feature useful if *some* developers don't make use of it?
What if the program is not available for their platform? At what level
is this feature implemented? Will it be available for all possible
clients and platforms?

There have been other systems that attempted client-side scripts
("triggers"). Not a good idea.

You can use server-side post-commit triggers, tho. Reduces a lot of variables.


On Thu, May 7, 2009 at 00:44, <webpost_at_tigris.org> wrote:
> Hi All,
> I got the idea of having some way of calling an external command after each commit. This could useful when developers always do the same things after a commit so that it can automatically done.
> One could, of course, write his own little script wrapping the svn ci command and adding the other external command... but this could simply integrated into svn.
> For example, I found that one could wish to have a file containing the version string of his software, e.g. as in major.minor.patch.revision. This file could be then hosted on a website an used for a "check for update" feature. However, it would painful to update that file and upload it to the website at every commit, hence the idea.
> What do you guys think ? Is it worth doing ?
> If so, I'd be happy to implement it...
> Cheers
> Dav
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2085925

Received on 2009-05-07 03:03:42 CEST

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