Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

Thanks all for your answers, after discussing it internally at Gradle, we won't be able to implement all those new (for us) requirements and maintain them over time without help. On Thursday, May 25, 2023 at 7:05:39 PM UTC+2 m...@basilcrow.com wrote: > In addition to what Mark wrote, I would

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

In addition to what Mark wrote, I would want to see some of our top open-source Gradle-based Jenkins plugins (e.g., Gradle, Terraform, Checkmarx, Jira Trigger, etc.) upgraded to use the latest gradle-jpi-plugin toolchain, a recent LTS release as the Jenkins core baseline, and a recent plugin Bill

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

On Thursday, May 25, 2023 at 9:07:41 AM UTC-6 at...@gradle.com wrote: Thanks for the quick answer! On Thursday, May 25, 2023 at 3:16:30 PM UTC+2 Mark Waite wrote: On Thursday, May 25, 2023 at 6:09:42 AM UTC-6 you wrote: Hi, lately I've been working on improving the Gradle support for

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

Thanks for the quick answer! On Thursday, May 25, 2023 at 3:16:30 PM UTC+2 Mark Waite wrote: On Thursday, May 25, 2023 at 6:09:42 AM UTC-6 you wrote: Hi, lately I've been working on improving the Gradle support for building Jenkins plugins, see

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

On Thursday, May 25, 2023 at 6:09:42 AM UTC-6 you wrote: Hi, lately I've been working on improving the Gradle support for building Jenkins plugins, see https://github.com/jenkinsci/gradle-jpi-plugin/issues/213 for more details Thanks for doing that. The latest JPI plugin release 0.49.0

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

Hi, lately I've been working on improving the Gradle support for building Jenkins plugins, see https://github.com/jenkinsci/gradle-jpi-plugin/issues/213 for more details The latest JPI plugin release 0.49.0 and recent changes on the pipeline-library

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

On Mon, Mar 27, 2023 at 7:27 AM 'Herve Le Meur' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > For those using buildPluginWithGradle() from the shared pipeline library, we could add a note about it in the logs. This was done in jenkins-infra/pipeline-library#629

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

For those using buildPluginWithGradle() from the shared pipeline library, we could add a note about it in the logs. On Wed, Mar 22, 2023 at 6:38 PM Basil Crow wrote: > Here are the most popular plugins still using Gradle for their build: > > gradle 232,746 > multiple-scms 22,241 >

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

Here are the most popular plugins still using Gradle for their build: gradle 232,746 multiple-scms 22,241 allure-jenkins-plugin 17,121 terraform 5,046 checkmarx 4,502 jira-trigger 3,996 blackduck-detect 2,838 npm-yarn-wrapper-steps 2,152 ez-templates 2,145 templating-engine 1,742

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

On Fri, Dec 16, 2022 at 7:43 PM sghil...@gmail.com wrote: > > Last I checked, generated poms were also invalid, which is a problem for > any consumers of these artifacts that do more than just download the hpi. > > I believe this was fixed in 2019 as v0.31.0 >

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

Hi all, I've been maintaining the gradle-jpi-plugin for the last several years. I'm in support of this decision. My most recent OSS plugin used maven as well to take advantage of the excellent tooling the community has put together. I elaborated a bit more on the mentioned issues in the

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

I submitted a dedicated issue on the plugin's repository outlining the TODOs and linking to this discussion. On Thursday, 8 December 2022 at 21:53:36 UTC+1 db...@cloudbees.com wrote: > On Wed, Dec 7, 2022 at 11:20 AM Alexander Brandes

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

On Wed, Dec 7, 2022 at 11:20 AM Alexander Brandes wrote: > There's no support for automated releases (CD, JEP-229), missing metadata > for the plugin page and a few other limitations, which don't make it a > great experience using it. > … > I would be ready to lift this restriction again if the

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

+1 On Thursday, December 8, 2022 at 8:27:13 AM UTC-8 Adrien Lecharpentier wrote: > +1 as well from me. > > Le jeu. 8 déc. 2022 à 17:19, Damien Duportal a > écrit : > >> +1 >> >> Le mercredi 7 décembre 2022 à 15:49:42 UTC+1, bma...@gmail.com a écrit : >> >>> +1. >>> >>> At least such a move

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

+1 as well from me. Le jeu. 8 déc. 2022 à 17:19, Damien Duportal a écrit : > +1 > > Le mercredi 7 décembre 2022 à 15:49:42 UTC+1, bma...@gmail.com a écrit : > >> +1. >> >> At least such a move will make it very explicit for any new plugin that >> only Maven really has /production/ support for

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

+1 Le mercredi 7 décembre 2022 à 15:49:42 UTC+1, bma...@gmail.com a écrit : > +1. > > At least such a move will make it very explicit for any new plugin that > only Maven really has /production/ support for Jenkins plugin dev. > > I think that we should still "allow" new plugins to use Gradle

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

+1. At least such a move will make it very explicit for any new plugin that only Maven really has /production/ support for Jenkins plugin dev. I think that we should still "allow" new plugins to use Gradle if they wish so. But then they'll be very well aware that they got to be ready for a lot

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

+1 On Wed, Dec 7, 2022 at 2:20 AM Alexander Brandes wrote: > > Hey everyone, > > the Gradle JPI plugin lacks fundamental support of the jenkins.io > infrastructure. > There's no support for automated releases (CD, JEP-229), missing metadata for > the plugin page and a few other limitations,

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

On Wed, Dec 7, 2022 at 11:20 AM Alexander Brandes wrote: > There's no support for automated releases (CD, JEP-229), missing metadata > for the plugin page and a few other limitations, which don't make it a > great experience using it. > Last I checked, generated poms were also invalid, which is

Proposal to ensure new plugin hosting requests use Maven instead of Gradle

Hey everyone, the Gradle JPI plugin lacks fundamental support of the jenkins.io infrastructure. There's no support for automated releases (CD, JEP-229), missing metadata for the plugin page and a few other limitations, which don't make it a great experience using it. Additionally, worth to