Ignore variations when JVM_OPTIONS is set #612
Merged
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 changeset causes variations from
playlist.xml
to be ignored, ifJVM_OPTIONS
env. variable is set. See also: #611Motivation:
If
JVM_OPTIONS
env. var is set, jvm opstions for test target get overwritten (including ones set by variation). In this case, test target is still repeated for every variation. However variations no longer make any sense (with overwritten JVM options). It just causes confusion and makes test target run longer.Testing:
with
JVM_OPTIONS
set: OK (multiple variations are NOT ran)without
JVM_OPTIONS
set: OK (multiple variations are ran)