Handle itests as part of the reactor during release #673
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
(for version bump etc.) Signed-off-by: Patrick Fink <mail@pfink.de>
Closed
14 tasks
davidgraeff
approved these changes
Mar 20, 2019
wborn
approved these changes
Mar 21, 2019
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.
This fixes a NPE by the unlesh plugin during a version bump. Cause of the NPE: Unit Tests are skipped during release to speed up the process, but itests won't be part of the reactor then even though its part of the POM hierarchy. This breaks some unleash internals.
Signed-off-by: Patrick Fink mail@pfink.de