odoo-tower/odoosky-odoo
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
2 Commits 1 Branch 0 Tags
3c8b1050c16ae71e5388e158aa46933413a99bba
Go to file
Clone
Open with VS Code Open with VSCodium Open with Intellij IDEA
Download ZIP Download TAR.GZ Download BUNDLE

README.md

odoosky-odoo

Pinned Odoo platform images for OdooSky v3.

Why this repo exists

Customer instances must pull from a Git-pinned, OdooSky-controlled image. The 2026-05-04 incident proved that pulling Docker Hub's rolling odoo:18.0 tag = inheriting whatever Odoo SA's nightly cron shipped that morning. Their May 4 build ships a SQL regression that breaks every login on every new pod.

This repo is the source of truth for which Odoo nightly each major is pinned to. The chart instance-template-v3 reads from this list. ArgoCD reconciles. Customer instances always pull a build we tested.

Where the images live

registry.odoosky.cloud/odoosky/docker-mirror/odoo:<pinnedTag>

Same registry path that already mirrors upstream images for BuildKit during addon builds. We're now also using it for runtime Odoo.

How to bump

See versions.yaml — the bump policy + smoke checklist live there. The shape: smoke first, push to mirror, update versions.yaml, commit.

What this is NOT

  • A build-from-source pipeline. Today we mirror upstream nightlies as exact bytes. Future enhancement: build from source at a pinned commit with our own patches.
  • An automated bump. P5 in the rollout plan adds a Gitea Actions job that auto-builds + auto-smokes new candidates and proposes bumps. Until then, bumps are operator-clicked on lab1.
Reference in New Issue View Git Blame Copy Permalink
Description
Pinned Odoo platform images. Source of truth for which Odoo nightly each major runs.
Readme 27 KiB