RE: Pre-commit hook

The only thing I can think of is to have your scripts be in a svn copy/branch of the main trunk. Have your build system check the scripts on commit and if no errors occur it can merge them to trunk, or just copy the scripts to trunk and commit them that way.

They would still be in source control but not in trunk until they have been verified.

BOb

From: Scott Vickery [mailto:svickery_at_cavucorp.com]
Sent: Friday, July 10, 2009 2:12 PM
To: Stephen Connolly
Cc: users_at_subversion.tigris.org
Subject: RE: Pre-commit hook

We are using CruiseControl for a similar thing.

What I am trying to do it to prevent faulty scripts get getting into source control in the first place. Developers test against a single database, but, we have 100's of databases. Right now, there is a process that is done on the side outside of version control to test the scripts against all databases. I am trying to integrate that process into version control to make check-ins part of our process instead of an afterthought.

Basically, I trying to reduce overhead on the developer. But, as has been pointed out, this is either a pre checkin activity OR a build issue.

Thanks,
Scott

________________________________
From: Stephen Connolly [mailto:stephen.alan.connolly_at_gmail.com]
Sent: Friday, July 10, 2009 2:02 PM
To: Scott Vickery
Cc: users_at_subversion.tigris.org
Subject: Re: Pre-commit hook
I would prefer a CI system such as Hudson that polls svn and checks out the scripts and runs them against your database.

using a pre-commit or post-commit hook is tight coupling your CI with your source control aka a bad thing

what happens when the database is down and you've left on holidays for two weeks? nobody can commit

Sent from my [rhymes with myPod] ;-)

On 10 Jul 2009, at 18:15, Scott Vickery <svickery_at_cavucorp.com<mailto: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?

Thanks,
Scott

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

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-10 20:29:56 CEST