-
Task
-
Resolution: Done
-
Minor
-
None
Continued from RHIDP-8172.
Problem seems to be that the label quay.expires-after=183d is only applied to ONE of the FOUR tags set when releasing the community images
Unclear if this is a bug in the docker/metadata-action@v5 workflow - seems likely so I've reported https://github.com/docker/metadata-action/issues/534
https://github.com/redhat-developer/rhdh/blob/main/.github/workflows/next-build-image.yaml#L194-L206
- name: Set container metadata (for releases, 183d expiry)
id: meta-release
if: ${{ env.REF_NAME_SHORT != 'next' }}
uses: docker/metadata-action@v5
with:
images: ${{ env.REGISTRY }}/${{ env.REGISTRY_IMAGE }}
tags: |
type=raw,value=${{ env.REF_NAME }}
type=raw,value=${{ env.REF_NAME }}-${{ env.SHORT_SHA }}
type=raw,value=${{ env.REF_NAME_SHORT }}
type=raw,value=${{ env.REF_NAME_SHORT }}-${{ env.SHORT_SHA }}
labels: |
quay.expires-after=183d
results in:
- 5 tags with expiry, and
- 3 with none
- relates to
-
RHDHBUGS-1991 Intermittent build failures when pushing tags and doing nightly builds
-
- Closed
-
-
-
- Closed
-
- links to
(2 links to)
