-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Develocity Gradle plugin is removed from convention plugin sample #1186
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should no integrate this PR.
@@ -1,7 +1,29 @@ | |||
plugins { | |||
id 'com.gradle.develocity' version '3.17.3' | |||
id 'com.gradle.develocity' version '3.17.3' // replace with this convention plugin once published |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure what you mean with this comment. There is no plan to publish this convention plugin. It serves as a template that other can copy and adjust to their needs.
convention-develocity-gradle-plugin/plugins/gradle-2-through-4/settings.gradle
Show resolved
Hide resolved
@erichaagdev Instead of adding the DV configuration to the settings.file, I would remove the DV/CCUD plugin declarations. The reason being that this project is an example of how to build a convention plugin, not how to configure a project with DV. |
@etiennestuder the motivation was that I ran the build and was prompted to agree to the Gradle ToS to publish a scan to
I chose option 1 to encourage and remind users that this build should also be connected to Develocity once it is copied. I chose But, maybe a better option is to remove Develocity Gradle plugin and CCUD as you say. We could then add this to the plugins {
// CHANGE ME: Apply your convention plugin once published
// plugin('com.myorg.convention-develocity-gradle-5-or-newer') version '1.0.0'
..
} This is the same pattern we follow for the rest of this template: Line 60 in 82714f7
What do you think about this? |
Yep. I fully agree with your option #2. |
fc7ba2e
to
0b9c965
Compare
0b9c965
to
e79b264
Compare
As it exists today, the user is prompted to publish the scan to
scans.gradle.com
. This is because the Develocity Gradle plugin is applied, but not configured.This change removes the Develocity Gradle and CCUD plugins.