Re: Next baseline shift

On Thu, Dec 1, 2022 at 10:15 AM Basil Crow wrote: > > Next week I will take a look at migrating from Jetty 9 to Jetty 10 in the plugin build toolchain. I released jenkins-test-harness 1912.v0cdf15450b_fb with a

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

Re: Next baseline shift

Prepared the draft PR for "buildPlugin()": https://github.com/jenkins-infra/pipeline-library/pull/541 Le jeudi 1 décembre 2022 à 19:16:40 UTC+1, m...@basilcrow.com a écrit : > I released the first tranche of PRs in 4.52 > . Next

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

+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