Contributors mailing list archives
Re: How to auto pull only selected folder (addon) from multiple OCA repo into one repo.by
ForgeFlow, S.L., Jordi Ballester Alomar
Your project AK is very interesting! Do you have a particular sample that you could send me so that we can play around with it?
One particular pain point that we face is that we'd really want to have a separate repo that does not contain the links, but the actual code, so that we can truly have a tight control on what code goes in to production, and what is the code diff between versions that are being released to production.
I find it interesting if I can have a customer-specific repo where all the addons used by the customer are aggregated, where I can tag the versions of code being released to production and quickly understand the diff.
So, this would mean to your AK project not maintaining links, but copying the actual code to a new folder. This aggregating process would be part of the development work, in preparation for a release to production.
On Mon, Jun 17, 2019 at 10:32 AM David Beal <firstname.lastname@example.org> wrote:
Hello kitti,Thanks to Pedro to present most of the tools. It seems they all use https://github.com/acsone/git-aggregatorSome of them are all in one solutions, but for your particular problematic I confirm it can be solved by symbolic links.You can have a look to this libDoc is not fully and update documentedBut here is the format you need to exposeYou see the format for merged branch and how to specify which modules (account-fin ...) are collected to 'links' directory gather all symbolic linksaddons path is then only : /odoo/src/addons', '/odoo/src/odoo/addons', '/odoo/links', '/odoo/local-src'finally `ak build` cmd : generate a repo.yaml file required by git aggregator which clone and update branchLet me know if you need informationMy 2 cts
David BEAL - akretion.comChef de projetOdoo Développement / IntégrationLe lun. 17 juin 2019 à 08:22, Kitti Upariphutthiphong <email@example.com> a écrit :Thanks you Pedro, I will take a good look at it.At first I was thinking about using Apache Airflow to automate git things (also to explore other aspect).On Sun, Jun 16, 2019, 6:07 PM Pedro M. Baeza (Tecnativa) <firstname.lastname@example.org> wrote:Hi, Kitti,With "manual" deployments, it's difficult to handle all the possible needs you have for an Odoo installation. Before created a deployment system, what I did is to git clone full repos, and add in the addons path only one extra folder, in which I made symbolic links of each addon I want to put in the database. With that, you only need to do git pull on each repository for updating it, but symbolic links will keep the same number of addons.But then, pull requests come to be important also, because you can't wait for the PR to be merged for having it in the installation. And also to auto-update concerning addons, and to have staging environment...So we created Doodba (DOcker ODoo BAse) as a general solution for deployment: https://github.com/Tecnativa/doodba. It includes all the tools that our know how have recommended over the time, with all these questions solved: we have an addons.yaml file where you declare the repository and the addons, and they are auto-populated. You can put in repos.yaml possible pull requests and they will be auto-merged in your deployment. Auto-update, protected staging environment, Mailhog for checking outgoing mails, etc is the set of features you have.For not being promoting only my solution, I have to say that other deployment methods have been done by other felow companies that are OCA contributors, like the pip system, packaging modules as pip packages and being able to do `pip install`, or other Docker based solutions like Dockery, Akretion docker-odoo or Camptocamp docker-odoo-project. Sorry if I miss any other one, but this is what I have in my head right now. Any other project can be mentioned as reply.Regards
Ecosoft Co. Ltd., Kitti Upariphutthiphong