> -----Original Message----- > From: Greg Stein [mailto:[email protected]] > Sent: Tuesday, 10 January 2012 4:13 AM > To: [email protected] > Subject: Re: [Trac-dev] Bloodhound / Trac Approach > > On Mon, Jan 9, 2012 at 12:44, Olemis Lang <[email protected]> wrote: > > On Mon, Jan 9, 2012 at 12:38 PM, Olemis Lang <[email protected]> wrote: > >> On Sat, Jan 7, 2012 at 7:30 PM, Gary <[email protected]> wrote: > >>> On 06/01/12 22:11, Hyrum K Wright wrote: > > [...] > >> > >> Another important subject to discuss should be CI setup . My proposal > >> initially is to have > >> > >> - Bitbucket mirror of Trac repos > >> - Bitbucket patch queues (to work on tickets) > >> - Bitbucket central patch queue archive (incorporating changes to > >> accepted patches) > >> - Jenkins CI @ testrun.org . In there I created once upon a time a > >> build job for > >> Trac XmlRpcPlugin so as to run tests on its Bitbucket patch queue . > >> - ... > >> > > > > but if course that's TBD . other alternatives like central SVN > > repository , ... can work together with this one way or another . > > ;) > > The ASF has a fully-supported set of Jenkins and Buildbot servers. I would > recommend using those rather than external servers, due to their better > support level. In fact, I suspect that Bloodhound will get even > *better* support since Gavin signed on to help with BH (he is the Infra > person who manages the build servers).
Sorry that I will be slightly late, due to a personal matter it will be about 2 weeks or so before I can join you all, rest assured I will catch up. Gav... > > Cheers, > -g
