[SPARK-57938][DOCS] Print active SKIP_ flags when Ruby doc build script runs - #58526
Open
nchammas wants to merge 1 commit into
Open
[SPARK-57938][DOCS] Print active SKIP_ flags when Ruby doc build script runs#58526nchammas wants to merge 1 commit into
nchammas wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
It's useful to know what skip flags are active when the documentation build runs. Instead of
echo-ing them in the places where we want to know, the build script now prints them itself when it runs.Extracted from #57010.
Why are the changes needed?
Helps troubleshoot builds when we want to know what exactly was supposed to run.
The new method to print flags is naive in that it prints all flags that begin with
SKIP_, even if they have no special meaning to the script. It's a minor tradeoff that lets us avoid repeating the names of every "real" skip flag.Does this PR introduce any user-facing change?
No.
How was this patch tested?
I ran the doc build locally.
Was this patch authored or co-authored using generative AI tooling?
No.