RE: Pre-commit hook

I understand... and the answer is no. As you said, this runs server side, the only feed back you can give is to return something to STDERR when it compeletes.

BOb

From: Scott Vickery [mailto:svickery_at_cavucorp.com]
Sent: Friday, July 10, 2009 1:44 PM
To: Bob Archer; users_at_subversion.tigris.org
Subject: RE: Pre-commit hook

Thanks for the input, but, my question is not about my process (yes, devs test before commit). The question is whether I can provide feedback to the user from a pre-commit hook.

Thanks,
Scott

________________________________
From: Bob Archer [mailto:Bob.Archer_at_amsi.com]
Sent: Friday, July 10, 2009 1:40 PM
To: Scott Vickery; users_at_subversion.tigris.org
Subject: RE: Pre-commit hook
>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

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2369901

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-10 19:57:39 CEST