At Coopdevs, in our odoo-role we use the tar
strategy to download and install an Odoo core version.
In order to generate a tar
archive, and to keep good track of which version we’re using in each instance, we create a release in our OCB mirror repository. We need to keep a mirror of the original OCA’s OCB since we’re (obviously) not allowed to create releases on the original one.
The mirrors are managed by Gitlab.com, in https://gitlab.com/coopdevs/migrated-projects/OCB repo you can find the mirror rules. This repository is a pull mirror of the original OCA’s OCB repository and then push the changes to our Gitlab instance in our OCB repo.
To modify the mirror rules, go to Settings > Repository > Mirror rules.
TODO: Why can’t we create a pull mirror directly in our Gitlab instance?
In ocb-automated-releases we have a pipeline that automatically creates OCB releases for version specified in
.gitlab-ci.yml
. It is scheduled to run every month, but we can manually trigger it in thePipelines Schedule
section of the repo.If you need to create releases from a version that is not listed in the file, simply edit
.gitlab-ci.yml
and update theBRANCHES
variable and run the pipeline.If you only need to create a release for a branch once, edit the
Manual Release of Custom Branch
pipeline schedule, set theBRANCH
version in variables and run it manually.
12.0
) and check that the latest commit is in sync with “upstream” (the original OCB repo). You can also check for errors in the sync looking at the repo’s settings, in the “Mirroring repositories” section. If the mirror is not in sync please contact the sysadmin teamDeployments
/ Releases section of our OCB mirrorTag name
field type the tag name you want to create (e.g. 12.0_2022-11-14
) and click on “Create tag”Create from
field is set correctly (it should match with the first part of the tag name, 12.0
in our example). You can leave the Tag message
empty.Release title
field with the same as the tag name, 12.0_2022-11-14
in our exampleCreate release
button located at the bottom of the page12.0_2022-11-14
in our case, in the odoo role odoo_role_odoo_release
variable (as an example please look at this case). Also, make sure that the odoo_role_odoo_url
variable is pointing to the correct OCB mirror.