-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
Upstream
-
3
-
False
-
-
False
-
-
-
Integration & Delivery - 261, Integration & Delivery - 262
-
0
-
0.000
Once pruning for cloud uploads, images, and builds is implemented, we need to automate the garbage collection (GC) runs within the release process. We should also explore the possibility of enabling versioning in AWS to ensure the GC runs smoothly and provides a backup in case any unintended changes occur in S3.
Current PR in pipeline to run the GC job in the release: https://github.com/coreos/fedora-coreos-pipeline/pull/1019
Also update the gc-policy.yaml to expand all kinds of pruning to all mechanical streams.