Ensure only snapshot jdbc driver versions are testing when running check #89560
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 was an interesting find. Because of the way we distinguish between
StandaloneRestIntegTestTask
andRestIntegTestTask
we were mistakenly running all BWC version tests when running thecheck
task on the JDBC driver projects instead of only snapshot versions.RestTestBasePlugin
by convention wires allRestIntegTestTask
s to thecheck
task. For our BWC testing, we instead createStandaloneRestIntegTest
tasks. These get fewer conventions applied, as they are typically used when manually wiring tasks, as is often the case with BWC testing. The JDBC driver tests are a form of BWC testing, but were mistakenly setup usingRestIntegTestTask
. We only want to test snapshot versions when runningcheck
. The full suite of versions gets testing in the periodic BWC job. This PR fixes this behavior such that we are only testing snapshot (in development) versions as expected.This is a very easy mistake to make so there definitely room for improvement here in terms of developer convenience. You can see in this build scan how the
check
task depends on the full suite of versions incorrectly.