containers/ws: Publish image more frequently, only when needed #22042
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As mentioned in #21969 (comment), the current method of pushing new
cockpit/ws
images to the registry is not optimal, as an image is pushed in regular intervals regardless of whether the Cockpit version changed. To not push an excessive number of images, a weekly schedule has been adopted, so that the container releases can be up to 7 days late after a new release landed in the Fedora repositories (this has also been discussed in #21950).This PR proposes the following changes:
FORCE_PUSH
for manual workflow dispatches has been added. If set totrue
, the image will be pushed to the registry regardless of whether an image with the current version is already present.