feat: introduce Maven configuration for GraalVM testing #314
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 PR introduces Maven project and Kokoro configuration for GraalVM native image testing.
With guidance from @lesv and @Neenu1995, our plan is to introduce changes that will be no-op (these change should not affect existing projects) while allowing individual repositories to opt-in GraalVM testing.
Summary of the changes proposed:
native
) which contains the dependencies and plugins to run all unit and integration tests compiled with GraalVM with a single command (mvn test -Pnative -Penable-integration-tests
). This should also be a transparent change for existing projects as the changes are only enabled with activation of the profile.A demo of this performed on the Secret Manager repo: googleapis/java-secretmanager#583
cc/ @suztomo