Skip to content

test(ci): canary — validate vendor-based matrix + aggregation on trunk#29

Open
liujinye-sys wants to merge 2 commits intoopen-vela:trunkfrom
liujinye-sys:test/trigger-trunk-ci-new-matrix
Open

test(ci): canary — validate vendor-based matrix + aggregation on trunk#29
liujinye-sys wants to merge 2 commits intoopen-vela:trunkfrom
liujinye-sys:test/trigger-trunk-ci-new-matrix

Conversation

@liujinye-sys
Copy link
Copy Markdown
Member

Purpose

Canary PR to exercise the trunk CI pipeline updated by open-vela/public-actions#58 (merged):

  • ci-tasks matrix reorganized into vendor-based groups: goldfish, sil, aurix, flagchip, qemu.
  • New qemu group (7 @cmake builds) and re-enabled flagchip/kcore0@cmake.
  • post-processing aggregates via needs.ci-tasks.result — correctly reports success only when every matrix instance succeeds.

Expected behavior

The CI workflow dispatched by .github/workflows/ci.yml (uses: open-vela/public-actions/.github/workflows/ci.yml@trunk) should:

  • Spin up 5 parallel ci-tasks runners, one per vendor group (fail-fast: false).
  • Produce build artifacts named Build_Package_goldfish, Build_Package_qemu, etc.
  • Run post-processing after all groups complete, reporting overall status based on needs.ci-tasks.result.

Notes

Open a PR against open-vela/packages_fe_examples:trunk to validate the
new vendor-grouped matrix and result-aggregation behavior merged via
open-vela/public-actions#58.
Bump the trigger file to resync PR and run the CI pipeline
with the vela_*.bin optional-copy fix and the post-processing
exit-1-on-failure change.
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