Migrate build to Develocity Conventions Maven extension #1426
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
corneil
approved these changes
Aug 7, 2024
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 PR migrates the build to use Spring's Develocity Conventions Maven extension.
https://github.com/spring-io/develocity-conventions
With this, explicit configuration of the Develocity Maven extension is no longer required, as all configuration is encapsulated within the Spring extension.
Additionally, build cache authentication now uses the Develocity access key, so separate build cache credentials are no longer required. The
DEVELOCITY_ACCESS_KEYenvironment variable is enough for both build scan publishing and remote build cache access.