-
Notifications
You must be signed in to change notification settings - Fork 689
New Docker Build for Zephyr Projects #12543
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
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
@pytorchbot label "release notes: none" |
2c31286
to
8766230
Compare
ca077f5
to
14d7fbd
Compare
larryliu0820
approved these changes
Jul 17, 2025
digantdesai
approved these changes
Jul 21, 2025
14d7fbd
to
c6fcc16
Compare
Conarnar
pushed a commit
to Conarnar/executorch
that referenced
this pull request
Jul 25, 2025
### Summary To officially support Zephyr and ensure CI tests code paths in the executorch repo that target builds for Zephyr, the environment that the CI runs in must have all the necessary packages and tools to build a zephyr project. This PR starts the process for supporting a new docker image that will have everything necessary to build executorch zephyr projects. This PR is prompted by the discussion on pytorch#12348. Eventually, CI tests will use the added Zephyr PAL for more in depth CI tests. ### Test plan Currently, the zephyr cmake preset relies on the `arm-sdk` docker image. This change adds a new `zephyr-sdk` image, and the `build-preset` test has been updated to use this new image. cc @larryliu0820 @jathu
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
ciflow/binaries
ciflow/periodic
ciflow/trunk
CLA Signed
This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.
module: arm
Issues related to arm backend
module: build/install
Issues related to the cmake and buck2 builds, and to installing ExecuTorch
module: ci
Issues related to continuous integration
release notes: none
Do not include this in the release notes
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.
Summary
To officially support Zephyr and ensure CI tests code paths in the executorch repo that target builds for Zephyr, the environment that the CI runs in must have all the necessary packages and tools to build a zephyr project. This PR starts the process for supporting a new docker image that will have everything necessary to build executorch zephyr projects. This PR is prompted by the discussion on #12348. Eventually, CI tests will use the added Zephyr PAL for more in depth CI tests.
Test plan
Currently, the zephyr cmake preset relies on the
arm-sdk
docker image. This change adds a newzephyr-sdk
image, and thebuild-preset
test has been updated to use this new image.cc @larryliu0820 @jathu