[CI] aggregate: trigger build-image via curl instead of gh CLI - #105
Merged
Merged
Conversation
The 'Trigger build-image workflow' step called `gh api`, but the self-hosted runner pool doesn't ship the gh CLI, so the step failed with "gh: command not found" (exit 127) and the aggregate run went red even though gitaggregate and the force-push had both succeeded. Replace the gh call with an equivalent curl POST to the repository_dispatch API (curl is universally available). Same event_type and client_payload; the no-token fallback is preserved.
dnplkndll
added a commit
that referenced
this pull request
Jun 14, 2026
The 'Trigger build-image workflow' step called `gh api`, but the self-hosted runner pool doesn't ship the gh CLI, so the step failed with "gh: command not found" (exit 127) and the aggregate run went red even though gitaggregate and the force-push had both succeeded. Replace the gh call with an equivalent curl POST to the repository_dispatch API (curl is universally available). Same event_type and client_payload; the no-token fallback is preserved.
dnplkndll
added a commit
that referenced
this pull request
Jun 19, 2026
The 'Trigger build-image workflow' step called `gh api`, but the self-hosted runner pool doesn't ship the gh CLI, so the step failed with "gh: command not found" (exit 127) and the aggregate run went red even though gitaggregate and the force-push had both succeeded. Replace the gh call with an equivalent curl POST to the repository_dispatch API (curl is universally available). Same event_type and client_payload; the no-token fallback is preserved.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The "Trigger build-image workflow" step in
aggregate.ymlcalledgh api, but the self-hosted runner pool doesn't ship theghCLI. The step failed withgh: command not found(exit 127), turning the aggregate run red after gitaggregate and the force-push had already succeeded — soaggregatedwas updated but the downstream image build was never dispatched.Replaces the
gh apicall with an equivalentcurlPOST to therepository_dispatchendpoint (curlis universally available). Sameevent_type(aggregated-updated) andclient_payload.sha; the no-token fallback is unchanged.