Hey, Thanks that got me on the right track. Documented what I was doing here: https://issues.jenkins-ci.org/browse/JENKINS-61827?focusedCommentId=390808&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-390808
Now mvn validate says the build is successful. However, it seems not the CI on Jenkins isn't working, the nodes are stuck on AWS with a connection problem. For Example: https://ci.jenkins.io/computer/EC2%20(aws)%20-%20High%20memory%20ubuntu%2018.04%20%20(i-0785c260cbb2a05fa)/ On Sunday, April 19, 2020 at 6:44:21 PM UTC+3, Tim Jacomb wrote: > > Hi Guy > > Timestamper and the two workflow plugins are in bom, I would still > recommend adding it, > > It looks like timestamper changed its group id at some point > > Thanks > Tim > > On Sun, 19 Apr 2020 at 14:09, Guy Sheffer <[email protected] <javascript:>> > wrote: > >> Hey Tim, >> That bom (pom.xml) does not seem to hold most of the plugins used in >> Configuration Slicing plugin. This is because the plugin slices settings of >> many plugins. Each plugin is included as a dependency. >> >> You can grasp the size of the list here: >> https://github.com/jenkinsci/configurationslicing-plugin/blob/devel/pom.xml >> >> Just to make sure, I went over the plugins and made sure, indeed quite a >> lot, including email-ext, ant, groovy and others are not in that POM. >> I am fairly sure I managed to get all the dependencies under gorup-id >> org.jenkins-ci.plugins up to date. That was easy because the pages are for >> the plugins are documented. However I cam not sure about other settings. >> Such as timestamper in org.jvnet.hudson.plugins or plexus-utils in >> org.codehaus.plexus . >> >> This is the final step to get this plugin to build with the new support >> for pipeline, so if someone with more experience than me could take a look >> its likely something simple I overlooked. >> >> Thanks for helping out, >> Guy >> >> On Monday, April 13, 2020 at 3:29:20 PM UTC+3, Tim Jacomb wrote: >>> >>> Normally you use the Jenkins bom >>> https://github.com/jenkinsci/bom >>> >>> Which includes the common plugins that are depended on, it saves a lot >>> of time when updating versions. >>> >>> Thanks >>> Tim >>> >>> On Mon, 13 Apr 2020 at 12:44, Guy Sheffer <[email protected]> wrote: >>> >>>> Thanks Oleg, >>>> To anyone that could help, >>>> I have got as far as updating all the versions by hand, but I am >>>> getting some RequireUpperBoundDeps errors. I am not sure what is the >>>> methodology to fix this, assuming now all the versions are up to date >>>> (which they might not be because I did this manually). >>>> I am really close to making a new release that supports pipeline build >>>> and would really appreciate figuring out this hopefully last step, will >>>> note that it does build on my local machine. >>>> >>>> Thanks, >>>> Guy >>>> >>>> https://issues.jenkins-ci.org/browse/JENKINS-61827?filter=21951 >>>> >>>> On Sunday, March 15, 2020 at 3:14:58 PM UTC+2, Guy Sheffer wrote: >>>>> >>>>> Hey, here is the information as requested in >>>>> https://wiki.jenkins.io/pages/viewpage.action?pageId=103088172 >>>>> >>>>> - >>>>> >>>>> Link to a plugin you want to adopt: >>>>> https://plugins.jenkins.io/configurationslicing/ >>>>> - >>>>> >>>>> Link(s) to pull requests you want to deliver, if applicable: >>>>> https://github.com/jenkinsci/configurationslicing-plugin/pull/21 >>>>> Note: this is not my code, however I want to build, fix and manage >>>>> the plugin >>>>> - >>>>> >>>>> Your GitHub username/id (e.g. oleg-nenashev for >>>>> https://github.com/oleg-nenashev/) >>>>> guysoft >>>>> - >>>>> >>>>> Your Jenkins infrastructure account id. Create your account >>>>> <https://accounts.jenkins.io/> if you don’t have one: guysoft >>>>> >>>>> Also, I tried to build the plugin and the build fails (test plugin fro >>>>> the tutorial works fine). >>>>> So I want to fix that first. >>>>> Build output here if anyone can tell me what is going on: >>>>> https://pastebin.com/reU1DbAt >>>>> >>>>> Thanks, >>>>> >>>> -- >>>> 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/1afbeb77-9f02-4e44-a8e4-38070deb864b%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/1afbeb77-9f02-4e44-a8e4-38070deb864b%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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/adeb4ba8-4c56-47d9-99b5-f499e5a1dc5d%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/adeb4ba8-4c56-47d9-99b5-f499e5a1dc5d%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/1d708d41-5425-4965-ba01-cd708a0e3122%40googlegroups.com.
