New maven message from hpi plugin 3.26?

The git client plugin, the git plugin, and the priority sorter plugin have updated their parent pom from 4.38 to 4.39. As a result of that, a new message appears from the hpi plugin. I'm not sure what change I should make to correct that new message or if I should ignore the message. The

Re: Jenkins 2.332.2 LTS RC testing started

On Wednesday, March 23, 2022 at 10:50:32 AM UTC-6 Ilde wrote: > Hello everyone, > > Latest LTS RC was made public and it is ready to be tested. Final release > is scheduled for 2021-04-06. > > Please, report your findings in this thread. > > I've been running the release candidate since shortly

Re: [JEP-229] Plugin CD workflow version scheme

Current version patterns in used based only on a subset of plugins I have in my instances are 1.0 1.0.0 1.0.0-0 2.v1234abcdef 1.2.v1234abcdef 1.0.2.v1234abcdef 1.0.0-2.v1234abcdef I think the knew CD workflow with the *documented version scheme and patterns*, either the default or the manual

Re: [JEP-229] Plugin CD workflow version scheme

The CD guide describes a scenario named "Manually controlled prefix*", *that outlines how to setup an example formatted as "major.minor", but you can break it down with ease to something like "major.minor.patch+build-hash" by

Re: [JEP-229] Plugin CD workflow version scheme

I am not a Jenkins plugin developer/maintainer, but I think if there was a supported semVer version documented in the https://www.jenkins.io/doc/developer/publishing/releasing-cd/ documentation and officially tested, it would allow devs to choose to use CD with interesting labels and SemVer

Re: [JEP-229] Plugin CD workflow version scheme

Heyo, I admit, the first time I stumbled apart major components releasing via CD last year, I was confused by it too, however, the more I read myself into CD, the clearer it became. The "build.hash" scheme is the default CD setup, if plugin authors choose to use a different setup, they can

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

Keeping the same groupId would definitively be the best solution. Let's see what's CloudBees' answer. Cyrille On Wednesday, March 30, 2022 at 8:02:43 AM UTC+2 m...@basilcrow.com wrote: > Hi Cyrille, > > On Wed, Mar 23, 2022 at 3:39 AM 'Cyrille Le Clerc' via Jenkins > Developers wrote: > > I