Import Kiwix-build container images

[kelson42]

openZIM and Kiwix CI/CD kiwix-build usage relies on container images with ready-to-use compilation environments.

These container images have been prepared within the kiwix-build repository so far, but this had a few inconveniences:

• Kiwix-build doing already many things, this was not simplifying the situation (see https://github.com/kiwix/kiwix-build/wiki/Kiwix-Build-usage-in-CI-&-CD).
• It's not the primary role anyway of Kiwix-build repository to prepare its runtime environment in the special use case of our CI/CD
• We have a dedicated repository for creating our container images and it's here

The only thing which has changed from the user point-of-view is that instead of making a Github release to generate a new release of the images, each time we merge to main, then a new tag with the current date is generated. dev versions continue to be made to each push (whatever on main or feature branch).

Once merged, we should reassigne the packages to this repository (in place of kiwix/kiwix-build).

[rgaudin]

Once merged, we should reassigne the packages to this repository (in place of kiwix/kiwix-build).

You can do it now by seeting the appropriate LABEL

[kelson42]

Once merged, we should reassigne the packages to this repository (in place of kiwix/kiwix-build).

You can do it now by seeting the appropriate LABEL

done

[mgautierfr]

Seems good to me. I have a question about versioning. We have a versioning based on tag on kiwix-build. Now it will based on date ? Is https://github.com/kiwix/kiwix-build/pull/646 should be updated then ?

[kelson42]

@mgautierfr Yes, do you mean the wiki page shouldbe updated?

[mgautierfr]

No, the workflows for CI and Release&Nightly which still use docker image version 38.

[kelson42]

@mgautierfr Not a problem, images are still available. Nothing to change right now.

[mgautierfr]

Not a problem I agree. But better to change to have a consistent configuration.