You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With automatic push working on main the task currently only runs post merge as part of the normal cirrus testing flow. Given there are not many PRs here but the base image may get updates we should have some cron based runs to periodically rebuild/push a new image.
The question is is how often should that run? Once day or week, something else?
Should we always push the new image even if nothing changed, if we always push a new image then the local "cache" by podman machine is not as useful as users would have to repull the image every day/week?
The text was updated successfully, but these errors were encountered:
Yeah for main nightly makes sense as we will basically always have changes due the podman-next copr you are right.
But I guess my question is more for release branches as well? I don't think spinning this daily there would add value as it would invalidate the download cache for users and unless the base image changed there are likely no actual changes in the image.
With automatic push working on main the task currently only runs post merge as part of the normal cirrus testing flow. Given there are not many PRs here but the base image may get updates we should have some cron based runs to periodically rebuild/push a new image.
The question is is how often should that run? Once day or week, something else?
Should we always push the new image even if nothing changed, if we always push a new image then the local "cache" by podman machine is not as useful as users would have to repull the image every day/week?
The text was updated successfully, but these errors were encountered: