← Back to team overview

openerp-community team mailing list archive

Re: Continuous integration for community addons

 

Dear Georges,


You're more than welcome on board :) I'm happy to see your work on buildbot. This is something we actually discussing internally. You are probably aware of our OERPScenario project that bring a higher level on tests writing, allowing more functional people to express the tests as sentences. Our last work on it was to introduce a DSL that allow to write the tests as fast as possible, which is greatly appreciated as tests writing could be boring ! The thing is... it's in Ruby. The community is hard to move on this language, even if we love it...

We are in the process of developing something here in Python ! Too early to talk about right now, but if we can work hands in hands on building a new buildbot with more test coverage on OpenERP, we're in !

Keep in touch on this topic. We'll probably contact you when ready on our side.

Best regards,


Joël




Le 29 nov. 2012 à 23:32, Georges Racinet <gracinet@xxxxxxxxx> a écrit :

> Hi,
> 
> I don't think we, Anybox, have officially reacted to the announcement of
> the new organization yet, but we of course welcome it heartfully and
> would be glad to help.
> 
> We have started continuous integration of some of these community addons
> with our buildbot based tool. We know that there are people not
> convinced by our approach, but it works right away and is quite simple
> and open.
> 
> As an experiment, we created a case for the branches belonging to the
> account-core-editors team.
> The result can be seen here :
> http://buildbot.anybox.fr/waterfall?builder=6.1-community-account-postgresql-9.1&builder=6.1-community-account-postgresql-9.2-beta3
> (this is a restricted view of http://buildbot.anybox.fr/waterfall)
> 
> Currently this is red, see at the end of this message about that.
> 
> Modifying or adding more such cases is just a matter of doing a pull
> request on a public repository on which the buidbot updates itself every
> night: https://bitbucket.org/anybox/public_buildbot_buildouts.
> 
> The configuration files themselves are simple enough (a buildout
> configuration, and a reference to it in MANIFEST.cfg) and mostly amount
> to a list of bzr locations and addons to install.
> 
> To get an idea of how it works, see this commit:
> https://bitbucket.org/anybox/public_buildbot_buildouts/commits/e194f2427759a07ad4e04c96f2aa0c99
> 
> and that whole file:
> https://bitbucket.org/anybox/public_buildbot_buildouts/src/4e5879c8f8994e6492d8a5734b9058cc7617f458/6.1-community-account.cfg?at=default
> 
> I don't want to enter into more details right now, but the system is
> much more powerful than this small experiment demonstrates, all of this
> is fully documented and we're available for questions if people are
> interested.
> 
> As a side note the current builds shows two problems with
> account-core-editors branches. Here's a link to the relevant log file :
> http://buildbot.anybox.fr/builders/6.1-community-account-postgresql-9.1/builds/9/steps/testing/logs/test.
> The first issue seems to be a true problem with some data, and the other
> one is the use of an old and deprecated OpenERP option about rounding.
> If I were more familiar with the modules being tested, I could certainly
> say more. Should I report them as bugs in launchpad ?
> 
> I also tried to create a case for sale-core-editors, but there's a
> dependency to a module I couldn't find in these newly extracted
> community addons (product_get_cost_field module).
> 
> Regards,
> 
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp

-- 

Joël Grand-Guillaume 
Division Manager
Business Solutions

Camptocamp SA
PSE A, CH-1015 Lausanne
http://openerp.camptocamp.com/

Phone: +41 21 619 10 28
Office: +41 21 619 10 10
Fax: +41 21 619 10 00
Email: joel.grandguillaume@xxxxxxxxxxxxxx


Follow ups

References