Gimera
Gimera manages multiple Git repositories and integrates them into a single workspace. In Zebroo projects it is what assembles an Odoo source tree: the Odoo core, Enterprise, OCA addon repositories and your own modules, each pinned to a known commit and optionally patched.
It is the reason a zodoo or zCICD project can reproduce the exact same addon landscape on a laptop, in CI and in production.
Why it exists
An Odoo project is rarely one repository. A typical setup pulls in:
- the Odoo core at a specific version
- Odoo Enterprise, if licensed
- several OCA repositories, each with its own release cadence
- Zebroo modules such as zSYNC
- local patches to any of the above
Git submodules can express some of this, but they make patching awkward and
leave you with a tree that is painful to work in. Gimera keeps a declarative
description of the whole landscape in one gimera.yml, and can materialise each
repository either as a real submodule or merged directly into the workspace.
The two integration types
This is the central concept.
| Type | What happens |
|---|---|
integrated | The repository's files are merged into your workspace at path. They become ordinary files in your project, and patches can be applied to them |
submodule | The repository stays a genuine Git submodule at path |
Zebroo projects use integrated almost exclusively — it produces a unified
source tree that Odoo can load directly and that patches can modify without
forking upstream.
Where to go next
| If you want to… | Read |
|---|---|
Understand gimera.yml | Configuration Reference |
| Run gimera | Command Line |