You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: build multiversion Javadocs in parallel with matching JDKs
Docs publishing runs make -C docs multiversion, but PR docs CI only ran make -C docs test. That left the publish-only multiversion and Javadoc path uncovered before merge.
Install Java 8 alongside Java 11 in the docs workflows and make the multiversion post-build helper select Java 8 for historical scylla-* and tag refs while keeping Java 11 for the current docs build. The helper still runs each checked-out ref's own docs/_utils/javadoc.sh, so older docs use their branch-local Maven and docs configuration.
Run make -C docs multiversion in PR CI and include docs workflow files in the docs workflow path filters so CI changes are validated before publishing.
Build multiversion refs with a repo-local parallel runner. It calculates version-level parallelism from os.cpu_count(), caps it at 8 workers, builds each version in an isolated temporary output root to avoid shared Sphinx theme asset races, then publishes completed outputs serially.
Give each version build its own temporary Maven local repository through MAVEN_OPTS so parallel historical Javadoc builds do not race on shared snapshot metadata.
Also make the current branch Javadoc script deterministic: skip install-time Javadoc attachment during the preparatory install, keep Maven parallelism with -T 1C, accept the current core/target/reports/apidocs output location with fallback to core/target/site/apidocs, and fail clearly when generated output is missing or empty.
0 commit comments