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 On Thu, 24 Oct 2019 at 05:24, Mark Waite <[email protected]> wrote: > > > On Wed, Oct 23, 2019 at 10:18 PM 'Gavin Mogan' via Jenkins Developers < > [email protected]> 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 <[email protected]> >> 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 [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/a0c31d5f-85c3-4e95-8278-6962497b2991%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/a0c31d5f-85c3-4e95-8278-6962497b2991%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DusKMFcmUUaa8gqUYda%2B2j3LKF01MGoARMTowCzWY2xBmQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DusKMFcmUUaa8gqUYda%2B2j3LKF01MGoARMTowCzWY2xBmQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > Thanks! > Mark Waite > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtE%2BiipQn6JRyMhcrOKDd%3DVXwg9DM1Q4Zk9f-rcFzd2g-Q%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtE%2BiipQn6JRyMhcrOKDd%3DVXwg9DM1Q4Zk9f-rcFzd2g-Q%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BiffCKn%3D7pg5WPJEgLLLzMga8b_jzO1agp5fXWxteG5rFQ%40mail.gmail.com.
