Skip to content

Conversation

@ramceb
Copy link

@ramceb ramceb commented Dec 8, 2025

This PR shows how a sphinx build can be moved to
the execution phase of bazel builds.

Addditionally, module documentation is now
imported from sphinx_docs_library targets of
dependent modules.

This pr depends on changes in
PR

This PR shows how a sphinx build can be moved to
the execution phase of bazel builds.

Addditionally, module documentation is now
imported from  `sphinx_docs_library` targets of
dependent modules.

This pr depends on changes in
[PR](eclipse-score/docs-as-code#327)
source_dir = "docs"

sphinx_docs(
name = "html",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to do essentially the same as bazel run :docs_combo_experimental except that it does not work incrementally but run sphinx-build from scratch all the time. This is good for determinism but slower when used interactively.

I proposed something similar in eclipse-score/docs-as-code#286 but we abandoned it because experience was that supporting multiple ways to build stuff was not reliable enough.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like a very similar approach. Thanks for the hint.

@ramceb ramceb closed this Dec 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants