Apps: community modules (OCA)

Find a module of the Odoo Community Association and add it to a development branch: no git submodule commands.

The Apps tab of a project lists the community modules of the Odoo Community Association (github.com/OCA) for the project's Odoo version: accounting reports, MIS Builder, the responsive web client, tier validations, queue jobs and thousands more. Adding one commits its OCA repository to a development branch as a git submodule, exactly what you'd do with git submodule add , without touching git.

Add a module

Find it Search by name, technical name or summary, or pick a category. Click a module to read its description, its dependencies and its license.

Add it to a development branch Tick one or more modules and choose Add to a branch… . Cloud Buddy shows what it will commit: the repository at oca/<repository> pinned to the version branch (for example 18.0 ), and the Python packages it adds to requirements.txt .

Let it build The commit is pushed to your GitHub repository and the branch builds as after any push. The dialog links to the commit and to the branch.

Install it in Odoo Open the build, then in Odoo: Apps → Update Apps List , search the module and Activate . Or tick Install them in this branch's builds : the branch then installs a list of modules (its own ones plus the new ones) in every new build.

Dependencies

A module that needs OCA modules from another repository (for example Account Financial Reports needs Date Range from server-ux ) shows them in the dialog: tick Add … too to commit both repositories together.

Python packages declared by the modules are added to requirements.txt once; the build installs them.

Programs (such as wkhtmltopdf ) must exist on the server: the dialog says so.

Getting it to production

Apps are only added to development branches. Test the module there, then merge the branch into staging and production like any change: the submodule and requirements.txt come with it. Pull request previews from forks never receive apps.

Updating a module The submodule is pinned to the commit the version branch had when you added it. To get newer fixes, update the submodule in your repository ( git submodule update --remote oca/<repository> ) and push.

The catalog is refreshed every week from GitHub. Modules marked as not installable by the OCA are not listed. Each module keeps its own license (AGPL-3 or LGPL-3 for most).