Only run Gradle compatibility tests against minimum and maximum release #898
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
stackoverflow
approved these changes
Jan 22, 2025
|
What about introducing parallelism instead of hoping (?) that each Gradle version in between works? This would also be scalable. No need to worry that this goes out of hand in the future... |
|
@StefMa from what I can tell, Gradle is actually kind of bad at executing multiple tasks within a single project in parallel. It can run multiple test classes in parallel (by setting This PR implements a simple workaround, but I'd be happy to accept a follow-up PR that parallelizes these :) |
Currently, we run against every release version, which is taking 20 minutes to run in CI, and this will grow as Gradle creates more releases. This limits the amount of Gradle versions being tested against; theoretically, only testing against the minimum version and the maximum version should ensure that we are compatible with every version in the range.
bioball
force-pushed
the
prune-compatibility-tests
branch
from
19273b5 to
8303436
Compare
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.
Currently, we run against every release version, which is taking 20 minutes to run in CI, and this will grow as Gradle creates more releases.
This limits the amount of Gradle versions being tested against; theoretically, only testing against the minimum version and the maximum version should ensure that we are compatible with every version in the range.