ci: zephyr west filter - #11344
Merged
Merged
ci: zephyr west filter#11344
Conversation
west update in every Zephyr job fetched 80 projects, about 140 seconds, and zephyr-tests did the same. The boards here come from seven vendors, so the other vendors' HALs, TF-M and the libraries the port never enables are left out of the import. 37 projects remain and the update takes about 60 seconds. Local west workspaces shrink the same way. hal_infineon stays: the Pico W's CYW43 lives there. nanopb stays: the port's Kconfig sources it.
Collaborator
|
@tannewt this looks good to me but want your look too. |
dhalbert
previously approved these changes
Sep 11, 2026
tannewt
requested changes
Sep 11, 2026
tannewt
left a comment
tannewt
left a comment
Member
There was a problem hiding this comment.
Awesome! Please add a note in the README under the "try any board" section that this may need to be changed.
The "Testing other boards" section says any Zephyr board can be built, which now depends on the board's HAL being in the manifest.
lynt-smitka
force-pushed
the
ci-zephyr-west-filter
branch
from
September 11, 2026 18:10
546deb8 to
2bdabd7
Compare
Author
|
It is ok? The manifest in zephyr-config/west.yml skips the HALs of vendors that no board here uses, so a board from one of them needs its entry removed from the name-blocklist and a west update to fetch it. For the esp32s3_devkitc board, that is hal_espressif |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
west updatein every Zephyr board job fetches 80 projects, about 140 seconds, and zephyr-tests does the same. The boards here come from seven vendors, so the other vendors' HALs, TF-M and the libraries the port never enables are left out of the import inwest.yml. 37 projects remain and the update takes about 60 seconds: 85 seconds off each of the 30 board jobs and 2 minutes off zephyr-tests. A local west workspace shrinks the same way.Tested on my fork with all 30 boards and zephyr-tests. Two projects that look unrelated have to stay:
hal_infineon, because the Pico W's CYW43 lives there, andnanopb, which the port's Kconfig sources.