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

Re: [PROPOSAL] post-commit should be able to report back to client

From: Adrian Hoe <mailbox_at_adrianhoe.com>
Date: 2006-01-01 15:03:30 CET

On Jan 1, 2006, at 8:43 PM, Joachim Durchholz wrote:

> Hi all,
> I'd like to have the post-commit script's output reported back to the
> client.
> This would be useful if the post-commit script does things that may
> fail.
> Use case
> --------
> We're using SVN not just for versioning but also for rolling out
> html and php files to a test server.
> I.e. the post-commit essentially does an "svn export" to the
> directory where the test server's Apache will look for it. "svn
> export" didn't always work, mostly due to permission issues.
> However, the error messages first got silently ignored (bad!), then
> logged to the system log (not much better, since looking at it
> requires root privilege), and we're finally considering writing the
> messages to a log file and mailing it to the committer (still not
> optimum).
> What we'd really like to have would be if the SVN client displayed
> the error messages from the script, just as it displays messages
> from the other hooks and from svnserve itself.
> Anybody willing to second this?
> This proposal has several tangents, but I wanted to check first
> whether it is useful at all :-)
> Regards,
> Jo

Happy New Year 2006!

Yes. I think it will be useful and more appropriate then.

We had an experience with an intern who was not familiar with version
control and made a mistake. What he actually did was either "svn rm"
or "svn mv". He "rm" the specific files when he still saw them in the
directory after the svn commands. When he commit his workcopy back to
server, an error occurred without any error messages from the post-
commit. His version was terribly ruined. With him forgetting what he
had done and no error messages received by project administrator, we
took some time to figure out what went wrong. It was a large
directory tree and many files in there. The trace back was painful
and time consuming. Finally, the project team managed to trace the
root of the problem.

I think that it is a good idea to execute some scripts with some
error messages if the commit was invalid. This will help to alert
project administrator if there is an error in commit.

"If you missed the rising sun and the morning dew, don't miss the  
beautiful sunset." -- Adrian Hoe inspired by Michal Nowak, June 15 2004
Received on Sun Jan 1 15:05:52 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.