-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Use manifest imports #1942
Use manifest imports #1942
Conversation
c8a2673
to
c745bbb
Compare
Yep, looks like CI is running 0.6. @thst-nordic -- I'm going to cut west 0.7.2 on Monday. Can the CI container be updated to include that when it's ready, so we can test this with that version? |
23d51a1
to
6695dd0
Compare
West 0.7.2 is out; ready for CI to use it to test this PR. |
be8dc55
to
f2ed593
Compare
@thst-nordic anything I can do to help get the CI container updated to use the new west? |
I made a new docker image with zephyr sdk=0.11.1, and with west=0.7.3, it will be used on next CI run. |
24788f5
to
44fdb78
Compare
7e200c8
to
aa7a18d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM now, thanks @mbolivar
89ed74a
to
b261057
Compare
@thst-nordic did I accidentally force push over something needed to test with west 0.7.2? I am seeing:
I don't think so, because the log for f2ed593 doesn't have anything that looks CI-related, but thought I should check. |
b261057
to
768e351
Compare
Looks like this is still blocked on a container update |
768e351
to
88e9003
Compare
88e9003
to
93a1417
Compare
@mbolivar can you please rebase it? |
93a1417
to
342c4a4
Compare
done |
@thst-nordic thanks for unblocking this! Here's what I see in the docs build:
I can't find a run_build.sh in the NCS anywhere, so I'm not sure how to debug. Any advice? My guess is there's a |
3075fe6
to
227ee2e
Compare
this is ready to merge after west.yml conflict fixed. |
227ee2e
to
1f68051
Compare
Use the west 0.7 manifest import feature to pull in projects from upstream Zephyr instead of maintaining them by hand. Use a name whitelist to get started with, to keep things explicit. This means the set of repositories from upstream has to be maintained by hand, but their paths and revisions no longer do. Whenever the zephyr "revision:" is updated, the paths and revisions of imported projects are kept up to date automatically by west. The NCS west extensions commands require west 0.7, but since that is now the minimum version required by the manifest and requirements.txt, there's no need to do special checking about that on our own here. Make some other changes to these extensions. Some are generic, others are specifically meant to deal with mergeups now that we're using imports. ncs-loot: - Skip output for each project unless there are OOT patches. (This is disabled in verbose mode.) - Only print the banner for a project after the loot has been calculated and we're ready to print it. - Add a hint about output being limited when --file is used. This argument can cause the total list of files output to be smaller than the output list. ncs-compare: - Improve the output for downstream patches which are merged upstream, using singular correctly if there's just one, and numbering the possibilities if there's more than one. - Use explicit paths on the user's computer when possible - When an imported project has fallen behind, the way to update it is by doing the zephyr mergeup. That way, we get the updated revision for free. Track imported projects and let the user know that's all they have to do if that happens. - Other miscellany both: - Print shorter --help lines. Control the indentation manually in descriptions. - use "NCS" instead of "nrf" Keep the development model document up to date, mainly with examples for how to use manifest imports in workflow 4. Add some other changes that follow from taking a look at this page in light of this new west feature. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
1f68051
to
5616a4a
Compare
Use the west 0.7 manifest imports feature in the NCS. This means we now require west 0.7. I will push a west 0.7.2 and make that our minimum version.
I have tested this on Arch Linux with a fresh init + update + build + flash + debug + debugserver + attach + list. No issues observed.
Users who are running west 0.6 will see this error:
So heads-up that if you see this error, you need west 0.7.
I also tested our NCS extensions and made some changes to keep their output usable now that the way we will be doing mergeups depends on if the project in question is imported or not.
CI fails because it's using west 0.6. We should update the CI container once west 0.7.2 is available early next week for more testing.