RE: New to subversion, need to find documentation on writing hooks

> -----Original Message-----
> From: Ted Byers [mailto:r.ted.byers_at_gmail.com]
> Sent: 21 May 2012 11:09
> To: 'Les Mikesell'
> Cc: users_at_subversion.apache.org
> Subject: RE: New to subversion, need to find documentation on
> writing hooks
>
>
> > -----Original Message-----
> > From: Les Mikesell [mailto:lesmikesell_at_gmail.com]
> > Sent: May-21-12 12:58 AM
> > To: Ted Byers
> > Cc: users_at_subversion.apache.org
> > Subject: Re: New to subversion, need to find documentation
> on writing
> hooks
> >
> > On Sun, May 20, 2012 at 4:16 PM, Ted Byers
> <r.ted.byers_at_gmail.com> wrote:
> >
> > > I have read arguments that recommend
> > > against this, claiming it can slow down commits, but then
> I am more
> > > concerned about code quality, and always having a
> codebase, which to
> > > me includes all tests, that compiles and runs properly
> than I am in
> > > the convenience of any programmers working on the project.
> >
> > I suspect that everyone involved would be happier if you
> implement that in
> a
> > continuous integration tool like jenkins that will still
> check everything
> (and can
> > do a lot more) but does not interfere with
> > commits. And use branches/tags to identify the production quality
> > versions so your programmers can get some work done.
> >
> > --
> > Les Mikesell
> > lesmikesell_at_gmail.com
>
> Hi Les
>
> Thanks
>
> I have never heard of jenkins. What more can you tell me about it?
>
> Cheers
>
> Ted
>
...it used to be called `Hudson` if you have heard of that.

Homepage : http://jenkins-ci.org/
Wikipedia : http://en.wikipedia.org/wiki/Jenkins_(software)

~ mark c
Received on 2012-05-21 12:13:44 CEST