Build stable branches periodically

[dtantsur]

Currently, quay.io images are only updated when a change merges to the corresponding ironic-image branch. This is not an issue on main (although it may become one if the development slows down there), but it's definitely a problem on stable branches, which this way to not receive new bug fixes from Ironic or updated dependencies.

One way to fix that is to create a periodic job that picks up new upper-constraints and either creates a PR against the corresponding branch or simply builds the image in Jenkins.

/kind ci
/triage accepted

[tuminoid]

If we want to simply build the image, we can add a schedule trigger to the GH workflow responsible for building the images. Just need to verify it passes the correct tags in case of a schedule. No need to involve Jenkins for this.

This however does not update the constraints, but it does pull the latest Ironic sources. I'm not a fan of changing the built result without a PR, so I'd very much favor the PR way. (Not a fan of unpinned Centos either, maybe we could pin that as well while at it, and include it in the update cycle?)

Secondly, we do push some fixes in the stable branches but unless there has been a vulnerability, we never release them. This is something we'd also want to fix.

Third, we need to fix the CS9/CS10 situation (CS10 never tested, just built). I have #747 coming when I Just find time to at least build it in PR testing, but its not optimal to just built stuff and never test it.

[metal3-io-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[tuminoid]

Do we want to close this, as we have Renovate bot pushing updates and thus we receive new images quite often?