Thanks all - I've got the build to work again by removing recommendedConfigurations and switching to explicitly building the minimum version of Jenkins that is referenced in the pom.xml for now. I also could fix the issue with upping the slf4jversion parameter but it seemed wrong to do this when I don't have any particular reason in the plugin to have that particular version. I guess I kind of expected the bom to handle that type of thing for me but I assume that's tracking what libraries were available for that particular version of Jenkins?
It would be useful if there was some kind of "minimum" configuration version defined which was defined by, say, the earliest LTS version which has greater than x% usage so that you don't have to keep as up-to-date as you seem to have to have to with recommendedConfigurations. Out of interest, is there a set of criteria about why a version is recommended? By my calculation (and it seems quite high so is possibly wrong) by moving from a minimum version of 2.164.3 to the recommended 2.222.3 would mean that about 60% of current users would drop out of support? (Sorry if this message seems confused but it kind of echoes my mind at the moment :D) Richard. On Sat, 2 May 2020 at 13:06, Mark Waite <[email protected]> wrote: > I misspoke, it was previously testing with Jenkins 2.164 and is now > testing with 2.222. Same principles apply. > > On Fri, May 1, 2020 at 7:03 PM Mark Waite <[email protected]> > wrote: > >> Yes, that's expected, at least in the sense that changes to the pipeline >> library are applied to repositories unless the repository specifically >> loads a precise version of the pipeline library. >> >> In this case, the change is a switch from compiling and testing with >> Jenkins 1.190.x to instead compile and test with Jenkins 2.222.x. That's >> part of the ci.jenkins.io buildPlugin() call for recommended >> configurations. >> >> Usually that hints that it may be time to consider updating the minimum >> Jenkins version supported by your plugin. >> >> As an example, I did some analysis of the Jenkins installed versions of >> the git plugin and decided that it is now time to update the minimum >> Jenkins version required for the git plugin. The current minimum version >> is Jenkins 2.138 (yes, that is a very, very old Jenkins version). The next >> git plugin release will require at least Jenkins 2.204. >> >> Mark Waite >> >> On Fri, May 1, 2020 at 6:52 PM Richard Bywater <[email protected]> >> wrote: >> >>> Just wondering if its expected that updates to Jenkins-Infra pipeline >>> library might cause issues on builds that have no changes to pom.xml etc.? >>> >>> Looks like there was a pipeline library change made between >>> https://ci.jenkins.io/job/Plugins/job/htmlpublisher-plugin/job/PR-56/1/ >>> and >>> https://ci.jenkins.io/job/Plugins/job/htmlpublisher-plugin/job/PR-56/2/ >>> which has broken the build due to library version issues such as : >>> >>> *12:28:10* Failed while enforcing RequireUpperBoundDeps. The error(s) are >>> [*12:28:10* Require upper bound dependencies error for >>> org.slf4j:jcl-over-slf4j:1.7.25 paths to dependency are:*12:28:10* >>> +-org.jenkins-ci.plugins:htmlpublisher:1.23-SNAPSHOT*12:28:10* >>> +-org.slf4j:jcl-over-slf4j:1.7.25*12:28:10* and*12:28:10* >>> +-org.jenkins-ci.plugins:htmlpublisher:1.23-SNAPSHOT*12:28:10* >>> +-org.jenkins-ci.main:jenkins-core:2.222.3*12:28:10* >>> +-org.slf4j:jcl-over-slf4j:1.7.25 (managed) <-- >>> org.slf4j:jcl-over-slf4j:1.7.26 >>> >>> Not sure if there's an issue with my pom.xml or similar that needs fixing >>> but thought it strange it would >>> suddenly break. >>> >>> Any help gratefully received :) >>> >>> Richard. >>> >>> -- >>> 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/CAAy0hwftkMA7_BTaW2tZj1-02WeyyVtWrWtSU6nKWMFP7jk7YA%40mail.gmail.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwftkMA7_BTaW2tZj1-02WeyyVtWrWtSU6nKWMFP7jk7YA%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/CAO49JtFAA62bnAue%3DiegAb04Fk0rvQDHqsc0k5O8BCuQPj6bsw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFAA62bnAue%3DiegAb04Fk0rvQDHqsc0k5O8BCuQPj6bsw%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/CAAy0hwdMy1ag%3DmF-346B56EUGTPSu2D9nGCkw3gE9b-epCKRPw%40mail.gmail.com.
