On Fri, Jul 10, 2009 at 13:15, Scott Vickery<svickery_at_cavucorp.com> wrote:
> I have a process in place that sanity checks SQL scripts. The user can take
> a list set of scripts which are then run against a series of databases to
> see if they run. The user is given feedback as they run. If the scripts
> fail, the user is told which database the script failed against.
>
> I want to put that process in place as pre-commit hook. So far so
> good. But, I would like to provide real time progress to the user that did
> the commit.
>
> Any ideas on how I could pull this off? AFAIK, the pre commit hook is only
> run on the server, and, there is no way for the user to see it. Correct?
Anytime a pre-comit hook script sends feedback to the user, it results
in a rejected commit. So you cannot give "real time progress" feedback
to the user.
Bob Archer is right, this should be done outside Subversion, maybe on
a build server as part of a CI process. Or better yet, by the user
*prior* to committing.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2369882
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-10 19:49:25 CEST