Disable caching of Dokka's integration tests #2826
Merged
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
Because integration tests are cached by default, it produces no output for showcasing documentation through S3 or GitHub artifacts. Regression from #2711
aSemy
reviewed
Jan 28, 2023
This was referenced Jan 29, 2023
Merged
TWiStErRob
reviewed
Feb 1, 2023
aSemy
reviewed
Feb 1, 2023
vmishenev
reviewed
Feb 7, 2023
Most likely yes, although I haven't checked. |
vmishenev
approved these changes
Feb 9, 2023
|
The argument applies to the whole build, the annotation only to one task. |
|
Not only that, but integration tests are run on TeamCity (I don't think it uses caches, but still) and are also run locally, so we'd have to be using |
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.
Because integration tests are cached by default, it produces no output for showcasing documentation through S3 or GitHub artifacts.
Tried to explain what needs to be done in the comment. I tried, but it takes too much time to implement and test it properly, and I'd like to restore the demo functionality sooner, so proposing to just disable it for now.
Regression from #2711