Autobuild latest gradle versions #277
Draft
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
…ons. Versions are filtered to be greater than 5.6 and to be a release version. To be able to keep our build matrix, the strategy there has to be changed to slice the set of discovered versions in a number of parts, and to select the part to run
vierbergenlars
force-pushed
the
autobuild-latest-gradle-versions
branch
from
c50aa32
to
a8a8b8a
Compare
vierbergenlars
force-pushed
the
autobuild-latest-gradle-versions
branch
from
1b3d947
to
28749d7
Compare
|
Kudos, SonarCloud Quality Gate passed!
|
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.
Extend the integration test logic to automatically fetch versions from Gradle.
For integration tests: Filter the list down to supported versions, and only run the highest of every minor version.
For the main test: Run the lowest and highest version.
Instead of based on hardcoded version numbers, the integration tests are split into slices, each having approximately the same number of versions to run tests for.