-
Task
-
Resolution: Done
-
Major
-
1.5.0, 1.6.0, 1.7.0
-
None
I found that we have https://github.com/redhat-developer/rhdh/actions/workflows/next-build-image.yaml?query=event%3Apush in place already for creating 1.y.z-commitSHA tags for each push of a tag to the repo, but it's only worked once out of 5 GA releases (1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1).
Additionally, it would be negligible effort to create a 1.6 tag at the same time as the 1.6.1-b7bf4c77 tag, so we should do that too.
Need to understand why the job is failing – perhaps it's a server load issue as the daily :next build happens at 3:18 UTC, whereas the tag trigger happens during the oft-busy 9-5 ET window.
Perhaps we can switch to `macos-latest-xlarge` runners?
- https://docs.github.com/en/actions/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners?search-overlay-open=true&search-overlay-input=ubuntu+arm+runners+vs+macos+runners&search-overlay-ask-ai=true
- https://docs.github.com/en/actions/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners?search-overlay-open=true&search-overlay-input=ubuntu+arm+vs+amd+runners&search-overlay-ask-ai=true
- or run everything on amd64 but use buildx to simulate arm?
- is cloned by
-
RHIDP-7979 ensure that the SHA used for floating tags in rhdh repo (for rhdh-local using community tags) MOVES with each re-tagging operation (1.5)
-
- Closed
-
- links to