Development builds are not getting quay expiration dates set
Closed this issue · 3 comments
Describe the bug
When container builds for tags other than releases or latest are created, they are supposed to have an expiration date in quay.io set. Currently, those expiration dates don't seem to be getting set.
To reproduce
Push changes to a development branch of a plugin that uses the ACT workflow. This should trigger a container build and push to quay.io, and you should see that the expiration date is not set.
Additional context
https://quay.io/repository/arcalot/arcaflow-plugin-sysbench?tab=tags
This is an issue with quay itself regarding multi-arch images. I believe they can be manually set, however, setting them on the images for build themselves automatically and pushing to quay does not seem to trigger whatever quay is looking for to set the expiration date according to their docs. I have already pulled each image and manually looked, and the images do have the correct labels. I will need to address this with quay itself. More to come.
Webb ended up creating a small script to do this for Pbench, using the Quay REST API: https://github.com/distributed-system-analysis/pbench/blob/main/jenkins/set-expiration
I will have to check into that thank you @dbutenhof . I also create a conversation in the gouprs that support quay.io. I will see what the tech support has to say. https://groups.google.com/g/quay-sig/c/P1s1er52aOE