Repository navigation
'Release' does not work 'external filter' #31
Description
Building the 'release' type of documentation does not respect the 'is_external' filter while it's building the 'needs.json'.
The reason is that at that moment, the imported 'module' is not external and is just building itself. Therefore the module has to NOT have any build errors / warnings, otherwise it will exit with an error => therefore the target after it (the one in our BUILD file) is not execute and won't run.
Best course of action is just to have modules that do not have errors in them :D I guess.
Just leaving this up here as a reminder.
Metadata
Metadata
Assignees
Labels
No labels
Activity
AlexanderLanin commentedon May 22, 2025
Released modules cannot have errors?! What's the problem?
MaximilianSoerenPollak commentedon May 22, 2025
I have to double check this as I already forgot somewhat.
But what I saw if I remember correctly was that the build from the module itself succeeded, but then the module as a target failed, without changing the underlying code.
But this might be a nonissue anymore.
MaximilianSoerenPollak commentedon May 26, 2025
Can be closed.