tools.bom not working for recent LTS version of jenkins?

[Mike Caspar]

Hi there.

I recently followed the instructions to switch to tools.bom to simplify dependency management.

For some reason, jenkins.version 2.176.4 (and others lower than this) work correctly.

However, 2.190.1 does not work (the most recent LTS version).

It appears that anything above 2.176.4 does not show up in the public maven repo.

2.190.1 of Jenkins is available, but I can't test compile against it using the BOM.

Can someone please let me know what incorrect configuration I might have or if there is something missing in the instructions?

Thanks

[Mike Caspar]

The error I get is...

Failure to find io.jenkins.tools.bom:bom:pom:2.190.1 in https://repo.jenkins-ci.org/public/ was cached in the local repository, resolution will not be reattempted until the update interval of repo.jenkins-ci.org has elapsed or updates are forced

[Gavin Mogan]

https://repo.jenkins-ci.org/releases/io/jenkins/tools/bom/

There's no 2.190.1 version there

I honestly don't know if there should be, is there a reason you need to compile your plugin with the latest lts?

Gavin

On Wed, Oct 23, 2019 at 9:04 PM Mike Caspar <mikecan...@gmail.com> wrote:

The error I get is...

Failure to find io.jenkins.tools.bom:bom:pom:2.190.1 in https://repo.jenkins-ci.org/public/ was cached in the local repository, resolution will not be reattempted until the update interval of repo.jenkins-ci.org has elapsed or updates are forced

--
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/a0c31d5f-85c3-4e95-8278-6962497b2991%40googlegroups.com.

[Mark Waite]

As far as I know, the plugin BOM for Jenkins 2.190.1 has not been released yet.  There are still issues that need to be resolved.  Use 2.176.x and jenkins.version=2.176.4 until it is released.

On Wed, Oct 23, 2019 at 10:04 PM Mike Caspar <mikecan...@gmail.com> wrote:

The error I get is...

Failure to find io.jenkins.tools.bom:bom:pom:2.190.1 in https://repo.jenkins-ci.org/public/ was cached in the local repository, resolution will not be reattempted until the update interval of repo.jenkins-ci.org has elapsed or updates are forced

--
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/a0c31d5f-85c3-4e95-8278-6962497b2991%40googlegroups.com.

--

Thanks!

Mark Waite

[Mike Caspar]

I make it a habit to test the latest LTS whenever I start doing some work to avoid future work and being surprised later.

I just recently switched to the new BOM approach today to make my life easier. 

I'll wait it out for a bit.

Thanks

Mike

[Mark Waite]

On Wed, Oct 23, 2019 at 10:18 PM 'Gavin Mogan' via Jenkins Developers <jenkin...@googlegroups.com> wrote:

https://repo.jenkins-ci.org/releases/io/jenkins/tools/bom/

There's no 2.190.1 version there

I honestly don't know if there should be, is there a reason you need to compile your plugin with the latest lts?

As part of my attempt to run the git client plugin automated tests with Jenkins 2.190.1, one of the paths being considered was to create a new release of the git client plugin which requires Jenkins 2.190.1 as its minimum version.  Since the git client plugino uses the plugin bom, it seems like it would need a 2.190.x release of the plugin bom.  That would allow the git client plugin to depend directly on trilead-api plugin 1.0.5, without the classloader related risks of depending on earlier versions of the trilead-api plugin when that plugin may not be available in earlier versions.  Refer to conversations on https://github.com/jenkinsci/git-client-plugin/pull/467 for more details.

However, it would not be very much work to create that 2.190.1 based git client plugin release without the plugin bom, then update it later when the plugin bom becomes available.

 

Gavin

On Wed, Oct 23, 2019 at 9:04 PM Mike Caspar <mikecan...@gmail.com> wrote:

The error I get is...

Failure to find io.jenkins.tools.bom:bom:pom:2.190.1 in https://repo.jenkins-ci.org/public/ was cached in the local repository, resolution will not be reattempted until the update interval of repo.jenkins-ci.org has elapsed or updates are forced

--
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/a0c31d5f-85c3-4e95-8278-6962497b2991%40googlegroups.com.

--
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/CAG%3D_DusKMFcmUUaa8gqUYda%2B2j3LKF01MGoARMTowCzWY2xBmQ%40mail.gmail.com.

--

Thanks!

Mark Waite

[Tim Jacomb]

There’s an open pull request for the latest LTS line

https://github.com/jenkinsci/bom/pull/110

I think the main reason for the delay is the trilead-api split from core has caused issues in a few plugins tests

Tim

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtE%2BiipQn6JRyMhcrOKDd%3DVXwg9DM1Q4Zk9f-rcFzd2g-Q%40mail.gmail.com.

[Jesse Glick]

On Thu, Oct 24, 2019 at 1:37 AM Tim Jacomb <timja...@gmail.com> wrote:
> I think the main reason for the delay is the trilead-api split from core has caused issues in a few plugins tests

Yes.

In the meantime, just use the 2.174.x BOM. For most purposes this
should be fine, even if the plugin declares `jenkins.version` to be
2.190.1.

If you simply want to test against 2.190.x without _requiring_ it,
leave your `jenkins.version` at something older (with a matching BOM),
and read the documentation for `buildPlugin`.