RE: Pre-commit hook
From: Bob Archer <bob.archer_at_amsi.com>
Date: Fri, 10 Jul 2009 13:39:49 -0400
>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?
Am I the only one that hears major warning bells going off here?
What does this script have to do with version control? It sounds like something that should be run on a build server. Or, perhaps it should be something done on the client first. Are you devs not following:
edit, update, TEST, commit workflow?
BOb
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
|
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.