Sal - sortable image tags to use with automation

[Jan Marchel]

What is needed from activeeon to enable cd process to pull newest images and redeploy the latest version is to introduce sortable image tags.

For instance, in zuul we use pattern:
'^master-[a-f0-9]+-(?P<ts>[0-9]{14})$'

Example how to do it in github:
https://fluxcd.io/flux/guides/sortable-image-tags/

[Ankica Barisic (akki55)]

Our latest image is always the same: activeeon/sal:dev

Meaning that will always pull the latest version available for NebulOuS

We will have just a dedicated image for release versions.

https://openproject.nebulouscloud.eu/projects/nebulous-collaboration-hub/wiki/sal-deployment-info#latest-image-httpshubdockercomractiveeonsal

I believe that in this case, you do not need sortable image tags as we have just two (dev and latest)

[Jan Marchel (janmarchel7bulls)]

Flux does not support selecting the latest image by build time.
Instead, it relies on image tags (e.g. v1.0, v1.1, etc.) to identify different versions of the image.

So to let flux-cd "know" if image is updated we need to create images like:

dev-2021-01-28.133158

then flux-cd track your dockerhub and looking for latest image with pattern 'dev-(?P<ts>[0-9]+)'
can update sal deployment with new image when it is builded

[Benguigui (mbenguig)]

We finally set up a dedicated jenkins job, triggered after each new commit to the sal master branch, and triggering a build of sal before building a sam docker image and pushing it under a sepcific tag (dev-<date>). Waiting for any new update to sal (on activeeon side) before checking on your side if you managed to consider the new pushed image.