Skip to content

fix: Pass the self-hosted image to the push jobs as an artifact - #55

Open
juho9000 wants to merge 1 commit into
codecov:mainfrom
juho9000:fix/self-hosted-release-artifact-handover
Open

juho9000 wants to merge 1 commit into
codecov:mainfrom
juho9000:fix/self-hosted-release-artifact-handover

Conversation

@juho9000

@juho9000 juho9000 commented Oct 9, 2026 •

Copy link
Copy Markdown

gazebo's self-hosted release 26.7.6 was tagged but codecov/self-hosted-frontend is
still at 26.4.1 (https://github.com/codecov/gazebo/actions/runs/28822509924). The
release workflow runs on pull_request: closed, and since June GitHub issues a
read-only cache token to runs for a merged PR, so the build job's cache save is denied
and Push Self Hosted Release Image fails on the miss. Same root cause and fix as
codecov/umbrella#2474.

The build job uploads the tarballs as a run-scoped artifact and the push jobs download
it. A second invocation in the same run (push rolling) reuses the uploaded image instead
of rebuilding; its download step in the first invocation reports an expected failure
(continue-on-error).

After merging, gazebo needs a new tag of this repo and a bump of its @v1.2.14 pin
before the next frontend release.

Refs codecov/umbrella#2371, codecov/feedback#963

Runs for a merged release PR get a read-only cache token, so the cache
save is denied and the push job finds nothing. No frontend release since
26.4.1 has reached Docker Hub.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant