Build p4-plugin using gradle.

[Sandeep Kumar]

Hi Team,

In the p4-plugin, I have made the switch from Maven to Gradle as the build tool using "gradle-jpi-plugin" (https://github.com/jenkinsci/gradle-jpi-plugin).

Before publishing, I want to gather feedback from the community to address any potential issues that may have been overlooked during this migration.

The Gradle file for the plugin can be found here: https://github.com/jenkinsci/p4-plugin/blob/master/build.gradle. Any insights or suggestions from the community would be highly appreciated.

Also, Which repository should be prioritized for publishing artifacts: https://repo.jenkins-ci.org/public/ or https://repo.jenkins-ci.org/releases?

P4-Plugin: https://github.com/jenkinsci/p4-plugin

Thanks
Sandeep Kumar

sku...@perforce.com

[Alexander Brandes]

> Any insights or suggestions

I would suggest staying with the maven toolchain, given the JPI plugin is feature stalled and we stopped onboarding plugins using Gradle over Maven more than a year ago.

If loss of functionality, stability, and support is no concern, you may use Gradle.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1e67637a-6da6-499e-9e0c-5c746d746ff6n%40googlegroups.com.

[Mark Waite]

I agree with Alex.  If you choose to transition from a maven based build to a gradle based build, you are also choosing extra work for yourself because you will need to track the improvements that are made in the maven build process.  It seems like that will be more work than you want to do.

Mark Waite