Update end-to-end tests to use the release Docker image or release archive #3576
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.
Description
This PR updates the end-to-end tests to make use release artifacts. This moves toward replacing the existing smoke tests with our end-to-end tests instead, though it doesn't complete that transition.
With this PR, our end-to-end test will use release artifacts. This means that our PRs will run tests against actual artifacts instead of test-specific artifacts.
This PR:
endToEndJavaVersion
option nameddocker
which runs using the release Docker image.buildSrc
to start sharing more logic between classes.tasks.register()
which allows Gradle to evaluate the tasks when needed.In order to make this work, I changed each test sub-project to register tasks from a configuration object. This configuration object has the correct configurations for creating the tests. Then the Gradle build will use the configurations to register the tasks. This works better than the old approach which called functions from the tasks. For one, it allows us to use
tasks.register()
and thus evaluate the tasks as needed.Issues Resolved
Resolves #3566
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.