Contributors mailing list archives


Re: Runbot long term to install packages and other features

Vauxoo, Moisés López Calderón
- 09/08/2016 15:51:29
Hello Mignon,

> We can resolve this dependency issue by pip installing the addons to test. It's what we do to test our new projects with buildbot at ACSONE.

if we use MQT we can use buildbot, buildout, ansible, ansbile + buildout...
But using a core integrator without additional configuration files or additional configuration process by project.

We have WIP PRs for this:

travis2docker will use MQT core scripts no matter what is the tool used inside (re-use code).
Other point is, if we change the process for runbot and the process for travis, we have 2 environments It could returns different result and is too complex to debug. More info in the first message of this thread point B) Reproduce travis errors

travis use a similar process and tools when you define a "sudo: false" in your .travis.yml

 - Use a big image of docker: (with packages pre-installed and cached folders)
 - Use a core integrator project.
 - Use AUFS.

2016-08-09 3:53 GMT-05:00 Alexandre Fayolle <>:
On 09/08/2016 01:08, Pedro M. Baeza (Tecnativa) wrote:
> It can be something to be done on the OCA sprint on Odoo days.

I was about to ask Moises if he was attending the code sprint.

I agree that this would be a good idea and a nice place to try out. We
have two servers for runbot, so we could probably keep one for the rest
of the sprinters and experiment on the second one.

Alexandre Fayolle
Chef de Projet
Tel : +33 4 58 48 20 30

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

Post to:

Moisés López Calderón
Vauxoo - OpenERP's Gold Partner
Mobile: (+521) 477-752-22-30
Office: (+52) 477-773-33-46
twitter: @vauxoo