Community mailing list archives
Re: OCA project: __unported__ folder considered painfulby
2015-03-11 8:27 GMT-06:00 Pedro Manuel Baeza Romero <firstname.lastname@example.org>:
Nhomar, one module (or also auto_install modules) per repo can be achieved, but joining via "git subtree" in the current repos. You will get the same number of repos to deploy. Also contributions to existing modules will be similar, but working on the subrepo. The only problem I see with this is with new modules, that need to create a new subrepo, and link it to the general repo.
I tested this option.
AFAICK it do not "autocommit" when one tree change on its repository, let's say:
I have a repository with:
--> subtree repository module_a.
--> subtree repository module_b.
--> subtree repository module_c.
Then, somebody make a commit on repository_a.
Its .travis trigger its tests may be red/yello and so on and repostory is not know of such change.
I think it is feasible, but in our complex multimodule enviroment with vertical dependencies (the ones in /_openerp_.py) and horizontal dependencies (the ones that are not mandatory but can cause conflicts for example the ones in res.config modules_* fields) it is really not feasible in practical PoV.
Again I tested internally and after 2 weeks I return my changes again. (and we have 5 persons in charge of such job) I don't want to know haow manage this complex dependency matrix with 500 modules and N combinations.
Camptocamp France SAS, Alexandre Fayolle - Camptocamp