Clarification for Dockerhub publishing of controller containers

[daniel-beck]

Describe your use-case which is not covered by existing documentation.

I was surprised by seeing the Docker container publishing job disabled today during publication of security updates.
This seems to be a preventative measure in case we'd re-publish old tags.

Please provide updated instructions how we should deal with this in the future. Should we just enable the MBPL, then scan for the new tag as usual, kick off a build, and once that's done (twice), disable the MBPL again?

Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.

No response

[lemeurherve]

This shouldn't be the case next time.

If it is, then yes "enable the MBPL, then scan for the new tag as usual, kick off a build, and once that's done (twice), disable the MBPL again" will be the steps to follow. (That's what I've done today)

A bit more details and links about old tags unexpected republication:

• Move docker controller images publication job from trusted.ci.jenkins.io to release.ci.jenkins.io #4999

[lemeurherve]

@daniel-beck as I don't know yet when we'll get rid of this job disabling/reënabling dance, do you have a suggestion to where I could put those instructions?

EDIT: I'll add them in the release checklist, let me know if you want them elsewhere too.

[daniel-beck]

@Kevin-CB please update our process doc accordingly.