Skip to content

Revert "ci: shorten the feedback loop (parallel jobs, warm Go cache, Build Cloud)" - #4223

Merged
aheritier merged 1 commit into
mainfrom
revert-4220-ci-improvements
Sep 10, 2026
Merged

Revert "ci: shorten the feedback loop (parallel jobs, warm Go cache, Build Cloud)"#4223
aheritier merged 1 commit into
mainfrom
revert-4220-ci-improvements

Conversation

@dgageot

@dgageot dgageot commented Sep 10, 2026

Copy link
Copy Markdown
Member

Reverts #4220

@dgageot
dgageot requested a review from a team as a code owner September 10, 2026 13:34
@aheritier
aheritier merged commit a907113 into main Sep 10, 2026
13 checks passed
@aheritier
aheritier deleted the revert-4220-ci-improvements branch September 10, 2026 13:45
aheritier added a commit that referenced this pull request Sep 10, 2026
Fork PRs receive neither repository variables nor an OIDC token, so the
image job failed on `DOCKERHUB_OIDC_CONNECTION_ID must be configured` for
the 60% of PRs that come from forks (the reason #4220 was reverted in #4223).
The old condition compared the PR's *base* repository to this one, which is
always true; trust is now decided on the *head* repository.

Trusted runs keep Build Cloud and both platforms. Fork PRs build linux/amd64
on the runner with a plain docker-container builder, no login, nothing
pushed, no build-record upload (the read-only token cannot create artifacts).
The Dockerfile is exercised for every PR instead of being skipped.
aheritier added a commit that referenced this pull request Sep 10, 2026
…ally

Fork PRs, PRs opened by Dependabot and other bots running with a read-only
token, and CI in forks of this repo receive neither repository variables nor
an OIDC token, so the image job failed on `DOCKERHUB_OIDC_CONNECTION_ID must
be configured` (why #4220 was reverted in #4223). The old condition compared
the PR's *base* repository to this one, which is always true.

The job now decides at runtime: Build Cloud (both platforms, one runner)
whenever the Hub OIDC connection id and the OIDC token endpoint are present,
otherwise a plain docker-container builder on the runner, linux/amd64 only,
nothing pushed, no build-record upload. Publishing runs still fail loudly
when Build Cloud is unavailable rather than downgrading. The Dockerfile is
exercised on every PR instead of being skipped or failing.
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.

3 participants