Repository navigation
Add reproducible Gradle build and application launch checks - #1
Merged
Merged
Conversation
This file contains hidden or 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
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.
Add Java 8 CI for the existing Gradle 5.2 wrapper. Replace the retired JCenter repository with Maven Central and correct the application-plugin entry point to match the existing package and executable-JAR entry point. CI builds and launches both the Gradle application and packaged JAR. The existing JUnit method is a placeholder; this workflow does not claim functional test coverage.
Validation: CI will exercise the actual repository checkout before merge; no test or document checks are skipped to make it pass.