Use local toolchain for docs build#15
Conversation
This reduces the amount of resources needed to build the documentation
License Check Results🚀 The license check job ran with the Bazel command: bazel run //:license-checkStatus: Click to expand output |
|
The created documentation from the pull request is available at: docu-html |
LittleHuba
left a comment
There was a problem hiding this comment.
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 |
|
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. |
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 suchticket yet, create one via this issue template.
Addresses eclipse-score/docs-as-code#339