1. Mailing Lists
  2. Contributors
  3. Re: OCA Addons Packaging next step

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: OCA Addons Packaging next step

Re: OCA Addons Packaging next step

Avatar

Re: OCA Addons Packaging next step

by
Camptocamp France SAS, Alexandre Fayolle
- 13/04/2016 09:10:37 
Hello all,

Sorry for the delay in doing my share of the work.
https://wheelhouse.odoo-community.org/ is now up. I also support
uncrypted http access but it can be removed if we thing this is not good.

Please report any problem here and I'll do my best to fix them.

Alexandre


On 06/04/2016 10:22, Bidoul@pad.odoo-community.org wrote:
> For reference, this is implemented with [1]
> 
> 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.
> 
> Best regards,
> 
> [1] https://github.com/OCA/maintainer-tools/pull/156/files
> 
> PS: as I side note it's interesting that I forwarded the last e-mail to
> 3 addresses (Alexandre Fayolle <alexandre.fayolle@camptocamp.com
> <mailto:alexandre.fayolle@camptocamp.com>>, Stéphane Bidoul
> <stephane.bidoul@acsone.eu
> <mailto:stephane.bidoul@acsone.eu>>, oca-beckport@odoo-community.org
> <mailto:oca-beckport@odoo-community.org>), the last one not existing.
> Nevertheless Odoo sent it to contributors@odoo-community.org
> <mailto:contributors@odoo-community.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
> <joel.grandguillaume@camptocamp.com
> <mailto:joel.grandguillaume@camptocamp.com>> wrote:
> 
>     If it is possible to do it on Travis, +1 !
> 
>     On Tue, Apr 5, 2016 at 11:38 PM, Moises Lopez <moylop260@vauxoo.com
>     <mailto:moylop260@vauxoo.com>> wrote:
> 
> 
> 
>         I don't know if is good for you travis way
>         Check follow example pylint-odoo-auto-deploy-pypi
>         
> 
> _______________________________________________
> Mailing-List: http://odoo-community.org/groups/contributors-15
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: http://odoo-community.org/groups?unsubscribe
> 


-- 
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
http://www.camptocamp.com

Reference