On Fri, Jul 10, 2009 at 14:11, Scott Vickery<svickery_at_cavucorp.com> wrote:
> 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.
Another thing to consider - how long will that check against hundreds
of databases take to execute? While that script is executing, no one
else will be able to commit. Such a process would be a very easy means
by which a developer could effectively DoS your repository and/or the
databases.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2369956
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-10 20:28:47 CEST