Hi Kristian, On 01/31/2014 11:18 AM, Kristian Nielsen wrote:

Daniel Bartholomew writes:

...

On Wed, Jan 29, 2014 at 4:01 AM, Alexander Barkov wrote:

...

Would it be possible to have buildbot watch branches which are on Launchpad, but which are outside of the /~maria-captains/ directory?

...

Sure. It can be configured to do so. Branches are defined using their

Note that currently Buildbot is hardwired to checkout branches under lp:~maria-captains. For example:

bzr_checkout = Bzr(baseURL="http://bazaar.launchpad.net/%7Emaria-captains/maria/", defaultBranch="5.1", mode="clobber", forceSharedRepo=True, timeout = 4*3600)

But that can be changed, of course.

One thing to be aware of is that putting a foreign branch into Buildbot gives full access to our buildhosts to anyone with ability to push to that branch. (That is one reason that we had the restriction to ~maria-captains/ so far).

Thanks for clarification! Then perhaps we should create trees for Kentoku in ~maria-capitains. Something like this: bzr+ssh://abarkov@bazaar.launchpad.net/~maria-captains/maria/10.0-mroonga/ bzr+ssh://abarkov@bazaar.launchpad.net/~maria-captains/maria/10.0-spider/

- Kristian.

Hi Daniel, On 01/31/2014 12:07 AM, Daniel Bartholomew wrote:

On Wed, Jan 29, 2014 at 4:01 AM, Alexander Barkov wrote:

...

Would it be possible to have buildbot watch branches which are on Launchpad, but which are outside of the /~maria-captains/ directory?

For example:

bzr+ssh://bazaar.launchpad.net/~mroonga/maria/mroonga/

Sure. It can be configured to do so. Branches are defined using their complete launchpad address. Buildbot just needs to also be configured so that it knows what to do with the branch once it has it. For example, buildbot currently knows what to do with MariaDB 5.1-5.3, 5.5-10.0, Java Client, and C client branches. As part of adding it to buildbot we would need to add everything that buildbot needs to know in order to build and test mroonga.

One question: Are we thinking of providing separate Mroonga packages? Wouldn't it make more sense to include this in MariaDB itself like we do with other storage engines?

The goal is to make Mroonga a part of the standard MariaDB distribution. However, we need a separate stage tree to test new features added by Kentoku, before merging them into the main 10.0. This is how it works with ConnectSE: Olivier pushes his changes to 10.0-connect. When 10.0-connect is green, we merge it into 10.0.

Thanks.