1. Mailing Lists
  2. Contributors
  3. Re: 14.0 branches

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: 14.0 branches

Re: 14.0 branches

Avatar

Re: 14.0 branches

by
Vauxoo, Nhomar Hernández
- 13/10/2020 00:26:16
BTW:

In my previous email, Share/Maintain and contribute cost us almost 0. (we expend 10 hours designing/discussing/programming vs 10 minutos sharing this).

El lun., 12 de oct. de 2020 a la(s) 17:24, Nhomar Hernández (nhomar@vauxoo.com) escribió:
Let me show graphically.

How do you audit a server?

dev-test-ci-production environments are as much alike as possible [1].

Then when debugging and development the flow to consume is:

Consume.
$ git pull repository.


Share and propose.
$ git checkout -b branch
$ git push
$ git PR.


With 5 commands 100% of the:

Test.
Update.
Staging.
Production

Are 100% the same (even the CHECKSUM OF FILES ARE THE SAME).

That mindset rely on git (impossible or at least more complicated with PIP).

An example of this working:

image.png


With 1 click I update all/audit and analize (in the image is our own vauxoo.com instance) we have more information without give access to our production server, but I hope it explains itself.

I hope it helps.

Good practice says: CI-DEV-TEST-PROD should be as equal as possible. (spotify is one of the best examples for this) https://github.com/spotify/luigi.

Distribution of the package I am 100% agree with PIP (that's not my point) my point is rely on PIP for the CI and come back to oca_dependencies.txt when this must be in the other way around, oca_dependencies.txt gererates the PIP package.

And force has only 1 way to do it.

Regards.

El lun., 12 de oct. de 2020 a la(s) 15:32, Graeme Gellatly (gdgellatly@gmail.com) escribió:
Hi,

Honestly I tried both ways. Trying to have nice neat build OCA installing modules. I even setup own Pypi server to distribute client modules. This is basically how the pip workflow worked.

pip install some_module
Oh it has a bug and I need to make a PR.
pip uninstall some_oca_module
git clone OCA/Web
git-aggregator file while PR waiting.

pip install some_other_module
rinse repeat.

Felt like every single module. Now maybe in a pure deployment environment pip works, maybe once a release is mature it does too and maybe I am a dinosaur and my workflow using git is stupid, but I just don't like using the python packaging for Odoo. Just too much stuff from too many different places. And unless every module you want to use is pip available then it just feels like 2 different processes even when there are no issues.

On Tue, Oct 13, 2020 at 9:12 AM Nhomar Hernández <nhomar@vauxoo.com> wrote:
Hello Daniel.

Yes I understand.

AFAIK there is a problem with the version in  pip.

How do you cohexsists 14-13-12-11 in the same environment?
How do you manage to do "from odoo import odoo" and falling apart virtualenv, how do you manage such coexistence?

I am pretty sure it is out of the scope from odoo (but they are not closed to do it) because the owner of the pip package is vauxoo.


Olivier asked us a few years ago to give it to them but then after a few conversations it was never a priority to them (but maybe that will change).

Regards.

PS: can you share the command to tray it from github?

I tried several options and I can't get it to work.

El lun., 12 de oct. de 2020 a la(s) 12:47, Daniel Reis (dreis@opensourceintegrators.com) escribió:
On 12/10/2020 11:07, Nhomar Hernández wrote:

Do you think Odoo will be pip-installable in some moment?


Just clearing this one, yes it is, thanks to some key contribution Stéphane made into the Odoo core.

Actually, I'll have a talk at the OCA Days called "pip install odoo":
https://odoo-community.org/event/oca-days-2020-online-training-and-learning-event-2020-10-15-2020-10-16-121/track/pip-install-odoo-61

I personally find it very convenient and use it everyday in my dev environments.
(Don't ask me about using it in deployment, my infrastructure team doesn't let me put a finger in their servers...).

Thanks
Daniel

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe



--

Nhomar G Hernández

Vauxoo | CEO

¡Construyamos algo genial!
Cel: +52 (477) 393.3942 | Telegram: nhomar | Twitter: @nhomar

México · Venezuela · Costa Rica · Perú

phone nhomar@vauxoo.com phone vauxoo.com/contactus  

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe



--

Nhomar G Hernández

Vauxoo | CEO

¡Construyamos algo genial!
Cel: +52 (477) 393.3942 | Telegram: nhomar | Twitter: @nhomar

México · Venezuela · Costa Rica · Perú

phone nhomar@vauxoo.com phone vauxoo.com/contactus  



--

Nhomar G Hernández

Vauxoo | CEO

¡Construyamos algo genial!
Cel: +52 (477) 393.3942 | Telegram: nhomar | Twitter: @nhomar

México · Venezuela · Costa Rica · Perú

phone nhomar@vauxoo.com phone vauxoo.com/contactus  

Reference