Closed jiridanek closed 1 week ago
Are we sure that sufficient time has been allocated to inspect the Trivy report before this workflow proceed to prune the images?
Are we sure that sufficient time has been allocated to inspect the Trivy report before this workflow proceed to prune the images?
I don't see it as an issue since the workflow prunes images that are 3 weeks old. We can always resort to the latest report/image if necessary.
we could push :latest
tags to ghcr and set the workflow to leave the newest image around, if we wanted to spend more time on this; before I did not want to have latest at all because hashes give so much more certainty all around
the workflow prunes images that are 3 weeks old
Ahhh ok i got it!
we could push :latest tags to ghcr and set the workflow to leave the newest image around, if we wanted to spend more time on this; before I did not want to have latest at all because hashes give so much more certainty all around
That's fine Jiri!
/lgtm /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: atheo89, caponetto, jstourac
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/retest
Description
Fixes #568
How Has This Been Tested?
See the action in action at https://github.com/jiridanek/notebooks/actions/runs/9717613825/job/26823642202#step:3:18
The repos this is cleaning are https://github.com/jiridanek/notebooks/pkgs/container/notebooks%2Fworkbench-images and https://github.com/jiridanek/notebooks/pkgs/container/notebooks%2Fworkbench-images%2Fbuild-cache
Merge criteria: