Clean up tasks & configurations, add shared testConfig #343
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
- makes XStreamMatcher available without exposing internals - adds KotestConfig to all projects: isolate tests, random order, parallelize
xeruf
force-pushed
the
chore/gradle-cleanup
branch
from
94791d5
to
e6e2870
Compare
SKoschnicke
requested changes
Dec 4, 2020
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.
This hopefully concludes the rampage in the last few days that ate up so many precious hours, trying to understand Gradle in depth.
One of the most important learnings & new features is a shared sourceset in the sdk, which via a configuration is depended upon in all projects to sync the KotestConfig and make util classes (currently only XStreamMatcher) available without exposing internals.
Other than that there are a few cleanups and fixes, nothing ground-breaking but generally improved cleanliness. @SKoschnicke should especially check the docker changes (7a93580).
Some related reading material: