Members mailing list archives

Re: help needed testing the runbot

Camptocamp France SAS, Alexandre Fayolle
- 23/03/2015 07:14:46
Hi Martin,

No there is no such documentation as far as I know. The basic working for a small runbot instance is fairly straightforward : install the addon just as you would install any other addon, maybe install some of OCA/runbot-addons modules too, then configure your repositories. I think you need to add one odoo repository and make your addons repositories depend on it.

Be aware that lots of things are going to be written in the runbot/static/ directory (git checkouts and instances), and that the user running the odoo process needs to have create database and drop database priviledges (this user is used to createdb, rather than the user configured on the instance).


On 20/03/2015 18:47, Martin Schmid wrote:
<blockquote cite="" type="cite">

very good.
I also want to use runbot for my own modules.
Is there a documentation how to install runbot?


Best regards from Germany

Martin Schmid (CEO)
Professional Scrum Master [PSM –]
Equitania Software GmbH

From: Alexandre Fayolle
Reply-To: "Odoo Community Association (OCA) Members"
Date: Donnerstag, 12. März 2015 14:25
To: Members
Subject: help needed testing the runbot


I'm sending the message here instead of community to avoid a slashdot
like effect. Please don't spread the word too widely for now.

We have made progress in the configuration and stabilisation of the OCA
runbot ( Many thanks to Sandy Carter
for his help on this.

The runbot is currently enabled for the following projects:

* OCB :
* connector (
* department (
* e-commerce (
* knowledge (
* l10n-canada (
* management-system (
* partner-contact (
* vertical-ngo (
* web (

Known issues:

* server-environment (in server-tools) poses problems. The server-tools
travis config file creates a symlink, we need to do the same with the
runbot. I'm investigating how I can set up something using stuff from
runbot-addons (
* server cleanup: the runbot does not cleanup nicely, and Sandy's
runbot_janitor addon was causing job failures, so we removed it. For
now, I have set up a weekly cron doing some cleanup, but I'm not yet
sure 1 week is short enough (especially when the load starts going up).
* not sure how the server will handle the load : there are lots of
repositories, and lots of branches, potentially lots of database connections

How you can help:

1. by reporting build failures which seem to be related to missing
dependencies, preferably on this mailing list or directly by mail to me.
Please don't use github chats for this, the message will be lost in the
tons of mails I get daily from there (they get filtered in a separate
mailbox that I process every now and then, more often then than now...)

2. by using the runbot, gently: connect to the instances to test the
PRs. Notify me of Error 500 you may get.

3. if you are an expert in configuring Linux / Postgresql to handle 100+
databases and odoo instances and 100+ users on these databases, then
your advice is very welcome (I'm mostly used to "small" setups with less
than 10 databases / server and 50 users)

4. I will progressively increase the load by activating the missing
repositories. If you feel any given repository deserves being activated
in priority, and you are willing to be especially watchfull on the
behavior of the runbot on the repository, please ask.

Thanks for you help,

Alexandre Fayolle
Chef de Projet
Tel : + 33 (0)4 79 26 57 94

Camptocamp France SAS
Savoie Technolac, BP 352
73377 Le Bourget du Lac Cedex

Post to:

Post to:

Alexandre Fayolle
Chef de Projet
Tel : + 33 (0)4 79 26 57 94

Camptocamp France SAS
Savoie Technolac, BP 352
73377 Le Bourget du Lac Cedex