ci: doxygen-checks: build the base coverage with the PR doc build system - #115170
Open
nashif wants to merge 1 commit into
Open
ci: doxygen-checks: build the base coverage with the PR doc build system#115170nashif wants to merge 1 commit into
nashif wants to merge 1 commit into
Conversation
The base branch coverage report was generated by copying doc/CMakeLists.txt and doc/Makefile from the PR branch into the base worktree and building there. That is a partial cherry-pick of the doc build system onto an old tree: as soon as a PR changes the build logic to reference something that does not exist on the base branch, the base build fails and the check blocks the PR. Point ZEPHYR_BASE at the base worktree and run the build from the PR checkout into a separate build directory instead. Everything the Doxygen configuration refers to is ZEPHYR_BASE-relative, so the sources being scanned come from the base branch while the entire build system, Doxygen configuration and scripts included, comes from the PR branch. Both coverage reports are therefore produced by an identical configuration, and no file is copied across branches. Nothing is built in the base worktree anymore, so its west update goes away as well; it was updating the module checkouts shared with the PR workspace to the base branch revisions. Assisted-by: Claude:claude-opus-5 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
zephyrbot
requested review from
fabiobaltieri,
henrikbrixandersen,
kartben and
stephanosio
August 2, 2026 15:25
|
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.
The base branch coverage report was generated by copying doc/CMakeLists.txt
and doc/Makefile from the PR branch into the base worktree and building
there. That is a partial cherry-pick of the doc build system onto an old
tree: as soon as a PR changes the build logic to reference something that
does not exist on the base branch, the base build fails and the check
blocks the PR.
Point ZEPHYR_BASE at the base worktree and run the build from the PR
checkout into a separate build directory instead. Everything the Doxygen
configuration refers to is ZEPHYR_BASE-relative, so the sources being
scanned come from the base branch while the entire build system, Doxygen
configuration and scripts included, comes from the PR branch. Both coverage
reports are therefore produced by an identical configuration, and no file
is copied across branches.
Nothing is built in the base worktree anymore, so its west update goes away
as well; it was updating the module checkouts shared with the PR workspace
to the base branch revisions.
Assisted-by: Claude:claude-opus-5
Signed-off-by: Anas Nashif anas.nashif@intel.com