Skip to content

[FEATURE BRANCH] add ext-ci pilot staging for a pre-merge dispatch test - #6331

Merged
thomas-bc merged 13 commits into
nasa:thomas-bc/ext-cifrom
JPL-Devin:devin/1793833143-ext-ci-led-blinker
Nov 5, 2026
Merged

thomas-bc merged 13 commits into
nasa:thomas-bc/ext-cifrom
JPL-Devin:devin/1793833143-ext-ci-led-blinker

Conversation

@thomas-bc-autowot

Copy link
Copy Markdown
Collaborator

Staging copy of #6328 (same branch, head d2045d3) into thomas-bc/ext-ci, so that ext-ci.yml exists on a nasa/fprime branch and can be dispatched manually before merge: gh workflow run ext-ci.yml -R nasa/fprime --ref thomas-bc/ext-ci -f pr_number=6328. See #6328 for the description and review record.

…rator)

Adds ext-ci-trigger.yml (no-op pull_request gate), ext-ci.yml (workflow_run orchestrator:
dispatch, poll, one Check Run per external repo, failed-only re-run, notify/block policy)
and .github/ext-ci-manifest.json onboarding led-blinker, zephyr-reference and
generic-hub-reference in the notify tier. Existing ext-*.yml workflows are untouched and
keep running alongside.
Same behaviour and workflows; folds in review findings: no automatic retry of the
non-idempotent dispatch call (a lost response falls back to dispatch_id correlation),
a failed check-status update is not treated as a failed dispatch, and a check whose
completion update failed is closed by the finalize step with the remote result.
…nifest source, compare 404, concurrency key)

- correlate/poll_all tolerate carried-forward entries (no remote_* keys) on a re-run
- a manual run with fprime_ref reads the manifest and ext ref from the branch the run was
  started from, not from the ref under test (any PR SHA is readable via /contents?ref=)
- a release push whose before SHA was rewritten runs everything instead of aborting
- concurrency group includes the event name so a PR branch named release/* cannot cancel the push run
Drop owner notifications (a notify repo is just a neutral check; no pull-requests/issues
write needed any more), failed-only re-run carry-forward (a re-run re-dispatches every repo),
the dispatch_id correlation fallback (the dispatch API returns the run id), manifest lookup
from the base branch and ETag polling.
@thomas-bc thomas-bc changed the title ci: ext-ci pilot staging for a pre-merge dispatch test (copy of #6328) [FEATURE BRANCH] add ext-ci pilot staging for a pre-merge dispatch test Nov 5, 2026
@thomas-bc
thomas-bc merged commit 0ff3e95 into nasa:thomas-bc/ext-ci Nov 5, 2026
78 of 83 checks passed
@thomas-bc-autowot thomas-bc-autowot added CI Issues pertaining to Continuous Integration python Pull requests that update python code labels Nov 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI Issues pertaining to Continuous Integration python Pull requests that update python code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants