Test Java 8 too on Azure Pipelines #1033
Merged
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
gdude2002
previously requested changes
Mar 12, 2019
gdude2002
reviewed
Mar 20, 2019
Coverage is probably identical on both.
|
Turned off JDK8 coverage. |
…toneMC/Glowstone into azurePipelinesMultiVersion
gdude2002
previously requested changes
Mar 24, 2019
gdude2002
approved these changes
Mar 25, 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.
Since Azure Pipelines allows up to 10 concurrent jobs, we can easily afford to run a second one per push, and it can help us ensure we're not breaking compatibility with JDK 8 (which I think some plugins still require). This PR adds a second job on JDK 8, and renames the jars from that second job; I'm not sure why there's only one coverage report.