Contributors mailing list archives
Re: OCA Addons Packaging next stepby
Acsone SA/NV, Stéphane Bidoul
For reference, this is implemented with 
This script does two things.
1/ add the setup.py to all repos. This is comparable to the update of README with the addons table or what transbot does in the sense it pushes to the git repos. So I don't think that part can/should be done with travis. In any case, that part is will disappear in the future when the setup.py are more and more fine tuned manually.
2/ generate all wheels on a nightly basis and publish them to wheelhouse.odoo-community.org on the OCA server. This could be done with travis but I'm not sure it's wise to have travis upload files to the OCA server.
When the time will come to push to pypi we can reconsider using travis for that. But there are still a few hurdles to overcome, such as:
* the dependency on odoo (which is not on pypi): I've no feedback from Odoo SA yet on that topic
* the fact that we need to maintain several series (8.0, 9.0) where pypi seems to be more geared towards having a single latest version of any given package; for Odoo addons we have several "latest" versions for a single package (one for 8, one for 9, etc)
* the fact that we currently generate a new package for each commit to an addon (using a "dev" version), that's fine for publishing to wheelhouse.odoo-community.org but it's not good practice to push all dev versions to pypi; to fix that we need proper release management of addons.
PS: as I side note it's interesting that I forwarded the last e-mail to 3 addresses (Alexandre Fayolle <email@example.com>, Stéphane Bidoul <firstname.lastname@example.org>, email@example.com), the last one not existing. Nevertheless Odoo sent it to firstname.lastname@example.org. So no harm here, the discussion is interesting, but be careful with Odoo mailing lists, kids. :)
On Wed, Apr 6, 2016 at 8:08 AM, Joël Grand-Guillaume <email@example.com> wrote:
If it is possible to do it on Travis, +1 !