Build Scan publishing is enforced for the Develocity Gradle plugin #801
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
gabrielfeo
approved these changes
Feb 19, 2025
jthurne
approved these changes
Feb 21, 2025
When running the scripts, we need to ensure a build scan is always published despite what the user has configured in their build. This was previously already the case for the Build Scan and Gradle Enterprise plugins.
erichaagdev
force-pushed
the
erichaagdev/always-publish-develocity
branch
from
4d40581 to
ecb66f8
Compare
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.
When running the scripts, we need to ensure a build scan is always published despite what the user has configured in their build.
This was previously already the case for the Build Scan and Gradle Enterprise plugins.