migrate to gradle develocity maven extension #1587
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
atomfrede
force-pushed
the
update-gradle-enterprise-plugin
branch
from
8b48468 to
73b213d
Compare
DanielFran
approved these changes
May 24, 2024
Member
|
@atomfrede should we run ng-default with develocity? |
Member
Author
|
@mshima You mean for a generated project? |
Member
|
Yes |
Member
Author
|
We do it for the auto generated sample, so with each release. I think thats enough (but I need to update the plugin for the generated gradle projects as well). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
We tried the migration in jh lite, right now something seems to be broken there (at least on ci). Let's try it with the bom project, to see if we have the same issue (not authenticated, but we are authenticated) :D