Skip to content

ci: swap Docker trigger-workflow-and-wait for JS workflow_dispatch#64

Draft
stormslowly wants to merge 3 commits into
mainfrom
ci/dockerless-workflow-dispatch
Draft

ci: swap Docker trigger-workflow-and-wait for JS workflow_dispatch#64
stormslowly wants to merge 3 commits into
mainfrom
ci/dockerless-workflow-dispatch

Conversation

@stormslowly

Copy link
Copy Markdown
Contributor

Draft / WIP — opened to verify the dockerless dispatch end-to-end. See TODO below before marking ready.

Why

convictional/trigger-workflow-and-wait is a Docker action, so the dispatch step only runs on Docker-capable Linux runners. Replacing it with the JS-based Codex-/return-dispatch + Codex-/await-remote-run pair makes the dispatch dockerless (runs on any runner, node24) and returns the downstream run_id directly.

What

  • ecosystem_ci_dispatch (from-pr) and ecosystem_ci_per_commit (from-commit): split the single trigger step into Dispatch (return-dispatch) + Await (await-remote-run), and feed the resulting run_id into ecosystem-ci-result and the action outputs.
  • rspack-ecosystem-ci-from-pr.yml: add a distinct_id input and a return-dispatch-id job that return-dispatch needs to correlate the dispatched run.

TODO before ready

  • ecosystem_ci_dispatch's return-dispatch ref: is pinned to ci/dockerless-workflow-dispatch for verification (commit c741cf0) — revert to main before finalize.
  • Apply the distinct_id input + return-dispatch-id job to the other five stacks' from-pr workflows and all from-commit workflows (cross-stack isomorphism).
  • Touches ecosystem_ci_dispatch/** + ecosystem_ci_per_commit/** → run the SHA Pin release + consumer pin bump per policy.

convictional/trigger-workflow-and-wait is a Docker container action;
on the mini runner there is no Docker daemon, so building its image fails.
Replace it with the-actions-org/workflow-dispatch (node20) in both
dispatch composite actions. Same wait/fail semantics; the downstream run
id is fed to ecosystem-ci-result unchanged.
…e24)

node20 is being deprecated and the-actions-org/workflow-dispatch is node20.
Use the Codex- two-step (node24): return-dispatch dispatches and returns the
run id, await-remote-run polls it to completion. return-dispatch identifies
the run by a distinct_id echoed in a step name, so the downstream workflow
gains a distinct_id input plus a tiny ubuntu-latest echo job (wired on
rspack-ecosystem-ci-from-pr.yml for verification; roll out to the rest once
green).
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