Hopefully fix build cacheability of jarSearchableOptions
#1375
Conversation
This file contains 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
|
Looks like CI is failing? But not 100% sure why Does that ring a bell? |
|
Thanks, Martin — this looks good to me! |
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.
Preamble: opening this PR as it's adding more context that an issue but I'm not 100% sure about everything that's going on in there. Feel free to close or modify this PR.
The issue is we have some tasks that are not cacheable because over overlapping outputs (build scan). My understanding is that
outputDiris the output ofBuildSearchableOptionsTaskand therefore the input ofJarSearchableOptionsTask. The output ofJarSearchableOptionsTaskbeing decided by archiveBaseName (here).Let me know what you think.