Skip to content

Use local toolchain for docs build#15

Open
NEOatNHNG wants to merge 2 commits intoeclipse-score:mainfrom
etas-contrib:local-toolchain-for-docs-build
Open

Use local toolchain for docs build#15
NEOatNHNG wants to merge 2 commits intoeclipse-score:mainfrom
etas-contrib:local-toolchain-for-docs-build

Conversation

@NEOatNHNG
Copy link
Contributor

Improvement

Important

Use this template only for improvement that do not influence topics covered by contribution requests or bug fixes.

Caution

Make sure to submit your pull-request as Draft until you are ready to have it reviewed by the Committers.

Description

This reduces the amount of resources needed to build the documentation.

Related ticket

Important

Please replace [ISSUE-NUMBER] with the issue-number that tracks this bug fix. If there is no such
ticket yet, create one via this issue template.

Addresses eclipse-score/docs-as-code#339

This reduces the amount of resources needed to build the documentation
@github-actions
Copy link

github-actions bot commented Jan 16, 2026

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run //:license-check

Status: ⚠️ Needs Review

Click to expand output
[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.3.0) and connecting to it...
INFO: Invocation ID: 33c551bc-3d83-42d7-bae6-da8f327b3374
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
WARNING: For repository 'googletest', the root module requires module version googletest@1.17.0, but got googletest@1.17.0.bcr.2 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 4 packages loaded
Loading: 4 packages loaded
    currently loading: 
Loading: 4 packages loaded
    currently loading: 
Loading: 4 packages loaded
    currently loading: 
Loading: 4 packages loaded
    currently loading: 
Loading: 4 packages loaded
    currently loading: 
Analyzing: target //:license-check (5 packages loaded, 0 targets configured)
Analyzing: target //:license-check (5 packages loaded, 0 targets configured)

Analyzing: target //:license-check (18 packages loaded, 9 targets configured)

Analyzing: target //:license-check (85 packages loaded, 9 targets configured)

Analyzing: target //:license-check (89 packages loaded, 9 targets configured)

Analyzing: target //:license-check (97 packages loaded, 9 targets configured)

Analyzing: target //:license-check (155 packages loaded, 2550 targets configured)

Analyzing: target //:license-check (158 packages loaded, 2558 targets configured)

Analyzing: target //:license-check (165 packages loaded, 3335 targets configured)

Analyzing: target //:license-check (168 packages loaded, 7524 targets configured)

Analyzing: target //:license-check (168 packages loaded, 7524 targets configured)

Analyzing: target //:license-check (168 packages loaded, 7524 targets configured)

Analyzing: target //:license-check (168 packages loaded, 7524 targets configured)

Analyzing: target //:license-check (172 packages loaded, 9531 targets configured)

Analyzing: target //:license-check (174 packages loaded, 9657 targets configured)

Analyzing: target //:license-check (174 packages loaded, 9657 targets configured)

Analyzing: target //:license-check (175 packages loaded, 9777 targets configured)

Analyzing: target //:license-check (175 packages loaded, 9777 targets configured)

Analyzing: target //:license-check (175 packages loaded, 9777 targets configured)

Analyzing: target //:license-check (176 packages loaded, 23062 targets configured)

Analyzing: target //:license-check (176 packages loaded, 23066 targets configured)

INFO: Analyzed target //:license-check (177 packages loaded, 25001 targets configured).
[7 / 13] Creating runfiles tree bazel-out/k8-opt-exec-ST-d57f47055a04/bin/external/score_tooling+/dash/tool/formatters/dash_format_converter.runfiles [for tool]; 0s local
[9 / 13] checking cached actions
[10 / 13] Generating Dash formatted dependency file ...; 0s disk-cache, processwrapper-sandbox ... (2 actions running)
INFO: From Generating Dash formatted dependency file ...:
INFO: Successfully converted 2 packages from Cargo.lock to bazel-out/k8-fastbuild/bin/formatted.txt
INFO: Found 1 target...
Target //:license.check.license_check up-to-date:
  bazel-bin/license.check.license_check
  bazel-bin/license.check.license_check.jar
INFO: Elapsed time: 222.075s, Critical Path: 2.42s
INFO: 13 processes: 9 internal, 3 processwrapper-sandbox, 1 worker.
INFO: Build completed successfully, 13 total actions
INFO: Running command line: bazel-bin/license.check.license_check ./formatted.txt <args omitted>
usage: org.eclipse.dash.licenses.cli.Main [-batch <int>] [-cd <url>]
       [-confidence <int>] [-ef <url>] [-excludeSources <sources>] [-help] [-lic
       <url>] [-project <shortname>] [-repo <url>] [-review] [-summary <file>]
       [-timeout <seconds>] [-token <token>]

@NEOatNHNG NEOatNHNG requested a review from a-zw January 16, 2026 15:25
Copy link

@a-zw a-zw left a comment

Choose a reason for hiding this comment

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

Looks good to me.

@github-actions
Copy link

The created documentation from the pull request is available at: docu-html

Copy link
Contributor

@LittleHuba LittleHuba left a comment

Choose a reason for hiding this comment

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

This is a really bad idea. While you might be faster short term, you will get into problems long term.
Just consider that when S-CORE is used within a project that brings cars to the road.
We have to ensure for several years to the future, that the software and documentation remains buildable.

I'm fine with merging this for the moment, but you should immediately consider working on a follow-up.

@FScholPer
Copy link
Contributor

FScholPer commented Feb 3, 2026

This is a really bad idea. While you might be faster short term, you will get into problems long term. Just consider that when S-CORE is used within a project that brings cars to the road. We have to ensure for several years to the future, that the software and documentation remains buildable.

I'm fine with merging this for the moment, but you should immediately consider working on a follow-up.

Same opinion. Whats the reason behind @NEOatNHNG

@AlexanderLanin
Copy link
Member

Is that something we can move to the general docs build? Its super annoying that bazel downloads all dependencies just to build docs. Or maybe there is some clever bazel flag or whatever.

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.

5 participants