lazarh.work

katyukha/Odood

Odood Releases v0.6.5 to v0.6.6-dev.1 Enhance Addon Management and CI Testing

Odood

The Odood project, designed to simplify Odoo addon development and server maintenance, has released versions 0.6.5-rc.1, 0.6.5, and 0.6.6-dev.1. These updates introduce new output formats for addon listings, improved release tooling, and enhancements to the CI environment, alongside fixes for process environment handling and addon uninstallation.

About Odood

Odood is a project aimed at simplifying the development and maintenance of addons for Odoo, as well as the deployment and upkeep of Odoo servers. Odoo is a popular open-source ERP system, and Odood provides tooling to streamline common tasks such as managing addons, releases, and testing environments. The project is used by developers and system administrators who work with Odoo installations and seek to automate and improve their workflows.

Key Updates in Recent Releases

Between the release candidates and the latest development versions, Odood has introduced several features and fixes that enhance addon management, release processes, and continuous integration (CI) testing.

New Output Formats for Addon Listings

Starting with version 0.6.5-rc.1 and continuing through 0.6.6-dev.1, the command odood addons list now supports output in Markdown (--md) and CSV (--csv) formats. This complements the existing table output and respects the same field selection options, allowing users to generate addon lists in formats suitable for documentation or further processing.

Similarly, the odood assembly sync command gained options (--addons-list-md and --addons-list-csv) to generate ADDONS.md and ADDONS.csv files. These files provide a readable list of addons available in an assembly, facilitating easier tracking and sharing of addon inventories.

Enhanced Release and Hotfix Commands

The release commands odood repo release and odood repo hotfix release were improved with new options:

  • -n or --dry-run to simulate the release process without making changes.
  • --addons-list-md and --addons-list-csv to generate and commit addon list files alongside the release.

These additions help maintainers verify release steps and keep addon documentation in sync with releases.

CI Docker Image Now Includes Headless Chrome

The CI Docker images (odoo-ci/{serie}) now ship with headless Google Chrome pre-installed. This removes the previous requirement to manually install Chrome to run browser-based tests, such as tours (HttpCase / browser_js). The production images remain unchanged, focusing the update on improving the continuous integration environment.

Fixes Related to Environment and Addon Management

Several fixes address environment variable handling and addon uninstallation:

  • Processes running the Odoo server and lodoo now have their HOME environment variable set to the server user's home directory rather than inheriting it from the caller (often root). This change aligns with standard practices used by su, sudo -H, and systemd, ensuring proper permissions and access.
  • PostgreSQL commands executed by odood deploy as the postgres user also run with the correct HOME directory, preventing unintended use of the caller's .psqlrc configuration.
  • It is now possible to uninstall addons from the database even if the addon files are no longer present on disk, addressing scenarios where addons have been removed but remain registered.
  • The odood repo do-forward-port command preserves key documentation files (CHANGELOG.md, CHANGELOG.latest.md, ADDONS.md, and ADDONS.csv) during forward-porting, and it fixes issues with translation file handling when no .pot files are present.

Implications for Users

These updates collectively improve the reliability and usability of Odood for developers and administrators managing Odoo addons and servers. The new output formats facilitate better documentation and integration with other tools, while the CI enhancements streamline automated testing workflows. Environment variable fixes reduce permission-related errors, and improved addon uninstallation support helps maintain clean database states.

Additional Context

While the release notes do not detail user reactions, the improvements align with common needs expressed in community discussions around Odoo addon management and deployment automation. The inclusion of headless Chrome in CI images, for example, addresses a typical pain point in running browser-based tests.

For more information or to access the releases, visit the Odood GitHub repository.

Sources