GitLab

logilab/cubicweb:dev instead of dev

Before this commit, the CI try to push «3.25».

feat: Update 'latest' tag to 3.29, release 3.29 image and update documentation with latest images for cubicweb 3.29

Heptapod does not support downloading archives of repo from an hg id (it exposes git id).
In order to invalidate docker cache, an url anchor with the hg id is used.

We checked non cubicweb images, so upgrades of cubicweb where not handled correctly.

So packages for cubicweb default branch are "3.28.0.dev0-1" instead of "3.27.2-1"

Followup 10e828efccf0, we must run "gen-static-datadir" and "i18ninstance" before starting the instance.
Otherwise <instance dir>/{data,i18n} may not be populated.

This include package 3.27.0rc1

We now have working repositories at:

deb http://apt.logilab.fr {stretch,buster} {main,cubicweb-{3.25,3.26}}

Use them instead of pip for base logilab/cubicweb images.

* All images now have a apt looking for packages in /repo
* Images for cubicweb 3.25 and 3.26 use packages from relevant repository
* logilab/cubicweb:dev image use the new "buildpackage" image to build a
  package from latest public changeset of cubicweb.

Packages to be installed differ given cubicweb and python versions, this is why
we introduce a PACKAGES build ARG.

We can now drop support for pip in "check-docker-updates.sh" script, since apt
list --upgradable will detect new packages.

We're going to switch the images to use cubicweb apt repository from apt.logilab.fr

For this introduce a "buildpackage" image which allow to build debian
package(s) and publish them to a local repo in /repo (which can then be copied
from a multi-stage build).

This allow to build docker images without using pip.

See documentation for use-cases.

Add a warning when building an image using "onbuild" tags.
Rework the documentation to make "onbuild" less documented and not the "first
example".

We deprecated onbuild images because too much magic occur with them, and
working with ARG/ENV on onbuild images is complicated.

They will probably be planned for deprecation on docker itself: https://github.com/docker-library/official-images/issues/2076

This will help users not using onbuild images to create an instance easily.

Since we're going to add new commands helpers in the docker image in following
changesets, introduce a "docker-cubicweb-helper" command that will be used to
add new commands.

Start replacing "get-cube" by "docker-cubicweb-helper get-cube".

Debian package for dev version of cubicweb doesn't build on stretch due to missing python3-pycryptodome.
Now that buster is the new stable, we don't want to maintain this stretch "dev" image.

This allows one, e.g., to request a backup.

Automatically upgrading the instance with --backup-db=no is not
desirable for anyone who cares about their data. Now that we have an
"upgrade" command, people should run this directly. Accordingly, we drop
the "check" part of upgrade.

This option has been dropped in 3.27, so our "dev" image wasn't working for upgrading instances.
It appear the option is useless in 3.26 too, since it only start and stop the
instance if a pid file exists, which is never true in the docker image.

Cube name might not be equal to the package name stripped by 'cubicweb-'.
For instance cubicweb-saem-ref cube name is "saem_ref", not saem-ref.

Use a python script to detect the cube name using pkg_resources.