Swatantra-66 commented on issue #20483:
URL: https://github.com/apache/nuttx/issues/20483#issuecomment-6126090661
Hi @acassis, @xiaoxiang781216,
Update: **Phase 1** has been completed and merged into `master` via PR
#20580 (persistent `ccache` caching across GitHub Actions workflow runs).
I am ready to proceed with **Phase 2: Chip / Architecture Build Filtering**
so that chip-isolated PRs (like #20477) don't trigger builds for all unrelated
chip defconfigs.
To ensure this aligns with your vision for the CI infrastructure, I'd like
your thoughts on the implementation approach:
- **Approach 1 (Granular Testlists & Matrix Routing)**:
Reorganize `tools/ci/testlist/arm-*.dat` into vendor/family groups (e.g.,
`arm-stm32`, `arm-nxp-imx`, `arm-sam`, `arm-nrf`, `arm-rp2040`, `arm-other`)
and update `.github/workflows/arch.yml` to only launch the matching matrix job
for isolated chip changes.
- **Approach 2 (Dynamic Filter in `testbuild.sh` / `cibuild.sh`)**:
Keep the existing matrix structure, but detect if the changeset is
strictly confined to `arch/<arch>/src/<chip>/**` and `boards/<arch>/<chip>/**`.
If so, pass a filter to skip non-matching board defconfigs during the run.
Would you prefer **Approach 1** (family-based testlists) or **Approach 2**
(runner target filtering)? Once aligned, I will prepare the implementation and
submit a PR.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
