ci: update CI trigger to include path that affects each CI tests - #326
ci: update CI trigger to include path that affects each CI tests#326HongNguyen635 wants to merge 1 commit into
Conversation
| paths: | ||
| - "include/**" | ||
| - "port/esp-idf/**" | ||
| - "port/freertos/**" |
There was a problem hiding this comment.
Is gating on freertos port changes intentional?
There was a problem hiding this comment.
yeah ESP-IDF is Espressif-flavored of FreeRTOS
| - "src/**" | ||
| - "samples/zephyr/**" | ||
| - "tests/zephyr/**" | ||
| - "west-ncs.yml" |
There was a problem hiding this comment.
Should we also gate on changes to zephyr/module.yml (in case blobs change)?
I do see run: west blobs fetch hubblenetwork-sdk done in the build, so it isn't strictly necessary, but it seems good to be explicit
Since zephyr-tests.yaml adds tools/ci/twister-quarantine.yaml, I would here too, for continuity. Like the above note, I think it isn't strictly necessary. i.e. a new build is quarantined because it broke due to a change in src/, the change in src/ would gate the build, and the build skips anything in the updated quarantine
There was a problem hiding this comment.
Good point I'll include the module.yml. For the quarantine, that was my initial thought as well, although I can add it for consistency with vanilla zephyr tests.
Update the CI build for each port to include paths to source code that would benefit from a CI rebuild to check for issues. Signed-off-by: Hong Nguyen <hong@hubble.com>
e3713eb to
1b2ec96
Compare
|
LGTM; will let someone with better CI experience complete final approval |
3 participants
Update the CI build for each port to include paths to source code that would benefit from a CI rebuild to check for issues.