Skip to content
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

Migrate from Gradle Enterprise gradle plugin to Develocity plugin #4135

Open
timtebeek opened this issue Apr 15, 2024 · 2 comments
Open

Migrate from Gradle Enterprise gradle plugin to Develocity plugin #4135

timtebeek opened this issue Apr 15, 2024 · 2 comments
Labels
recipe Requested Recipe

Comments

@timtebeek
Copy link
Contributor

What problem are you trying to solve?

Starting with version 3.17, the plugin is available under the “Develocity” brand. Please see the Develocity Gradle Plugin User Manual for the latest documentation. Several core functionalities have been deprecated with the rebranding and will be removed in a future plugin version. Therefore, upgrading to the 3.17+ version of the plugin requires more than just updating the version number.

Start by updating the plugin’s version to 3.17 and changing the plugin ID to com.gradle.develocity. If you are using the common-custom-user-data-gradle-plugin, update the plugin’s version to 2.0. After running a simple task like ./gradlew help you will be informed about the usage of the deprecated APIs:

Most of the violations can be fixed by replacing references of gradleEnterprise with develocity. Some APIs have been replaced by more descriptive and idiomatic alternatives. In this example, those APIs are taskInputFiles and publishAlways(). See Breaking API changes section for this and other examples. After these changes, your build script should look like the following:

https://docs.gradle.com/enterprise/gradle-plugin/legacy/#develocity_migration

@timtebeek timtebeek added the recipe Requested Recipe label Apr 15, 2024
@Bananeweizen
Copy link
Contributor

duplicate of #4134. @timtebeek looks like you had a network glitch

@timtebeek
Copy link
Contributor Author

ah no they are subtly different; one is for Maven and the other is for Gradle; Both need their own recipe for the migration. Thanks for checking though!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
recipe Requested Recipe
Projects
Status: Recipes Wanted
Development

No branches or pull requests

2 participants