BOM build errors due to conflict of baseline 2.319.3 and 2.319.1

[Ullrich Hafner]

I recently updated my plugins to follow the new guidelines to use 2.319.3 rather than 2.319.1 as a plugin baseline. But now all my plugin upgrade PRs fail in the BOM project (https://github.com/jenkinsci/bom/pulls). What do I need to do to get those PR builds working?

[jn...@cloudbees.com]

Hi Ulli,

Can you clarify what these guidelines are and where they are (I did not see anything in a scan of the ML, nor on jenkins.io)?

With my Jenkins user hat on I would be somewhat annoyed if I had to upgrade Jenkins to get a small bug fix for a plugin.

Upgrading to every  `.1`  LTS is ok - but I am surprised there is any guideline saying to update to a `.2` and a `.3`?

/James

[Ullrich Hafner]

Am 13.06.2022 um 11:11 schrieb 'jn...@cloudbees.com' via Jenkins Developers <jenkin...@googlegroups.com>:

Hi Ulli,

Can you clarify what these guidelines are and where they are (I did not see anything in a scan of the ML, nor on jenkins.io)?

With my Jenkins user hat on I would be somewhat annoyed if I had to upgrade Jenkins to get a small bug fix for a plugin.

Upgrading to every  `.1`  LTS is ok - but I am surprised there is any guideline saying to update to a `.2` and a `.3`?

/James

https://www.jenkins.io/doc/developer/plugin-development/choosing-jenkins-baseline/

There was quite a long and controversial discussion around that topic in this mailing list (and the associated PR). 

On Friday, June 10, 2022 at 5:49:14 PM UTC+1 ullrich...@gmail.com wrote:

I recently updated my plugins to follow the new guidelines to use 2.319.3 rather than 2.319.1 as a plugin baseline. But now all my plugin upgrade PRs fail in the BOM project (https://github.com/jenkinsci/bom/pulls). What do I need to do to get those PR builds working?

--
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/38dccdf2-2b81-422c-9202-74f2584b410bn%40googlegroups.com.

[jn...@cloudbees.com]

> There was quite a long and controversial discussion around that topic in this mailing list (and the associated PR). 

Thanks Ulli, for some reason I missed that, which is a shame.

I can not help you wrt the BOM specifics, perhaps Jesse/Basil or Tim can help.

/James

[Tim Jacomb]

Hi Ulli

Since you've bumped past a baseline that is still supported in bom you need to pin the previous version of the dependency in the bom that your plugin doesn't support now.

i.e. add

echarts-api 5.3.2-1

to

https://github.com/jenkinsci/bom/blob/master/bom-2.303.x/pom.xml

Thanks

Tim

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ae9415ea-6764-4b21-ae87-217f185e5af4n%40googlegroups.com.

[Ullrich Hafner]

I see, thanks! 

Shouldn’t the BOM also follow our guidelines and support only releases 2.303.3 and 2.319.3 and newer? There is a 2.289.x folder in there as well.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bic1AiFfzHRGkE_gKqf2ioF32iu5ZgnUkntuKoqB5H-7zg%40mail.gmail.com.

[Jesse Glick]

On Mon, Jun 13, 2022 at 12:43 PM Ullrich Hafner <ullrich...@gmail.com> wrote:

Shouldn’t the BOM also follow our guidelines and support only releases 2.303.3 and 2.319.3 and newer?

Perhaps. The current guideline for the plugin BOM is stated here: https://github.com/jenkinsci/bom/#lts-lines