I was expecting the usual litany what I'm not confident currently with pipeline on Maven core is that we have for example the "maven-3.x-jenkinsfile/MNG-6242 - build #1 - null" message, with this "null" part that makes me wonder if we are using it as expected.
And for large multi-module svn trunks (the ones we don't migrate to git: mainly plugins and shared), is there a solution to rebuild just changed modules? ideally, the rebuild when a SNAPSHOT dependency is published would have been a plus, but this is sufficiently a rare use that I won't be extremist Then IIUC, this migration job is one additional TODO for me... Regards, Hervé Le vendredi 6 octobre 2017, 17:46:53 CEST Arnaud Héritier a écrit : > I agree that we should use pipeline nowdays > perhaps a shared lib if we want to standardize some stuffs and a set of > multi-branches jobs (or org folder but it requires GitHub :( ) > > On Fri, Oct 6, 2017 at 9:16 AM, Stephen Connolly < > > [email protected]> wrote: > > On Fri 6 Oct 2017 at 06:32, Hervé BOUTEMY <[email protected]> wrote: > > > I just fixed a few failing jobs [1] to have again a usable Jenkins. > > > > > > Now I'm facing some issues, I suppose caused by newer Jenkins versions: > > > - Maven 3.0.5 causes NoSuchMethodError: o.c.plexus.util.xml.pull. > > > > MXParser > > > > > [2] > > > - I had to switch to JDK 8 for maven-plugin-tools job, since JDK causes > > > failures (looks like Jenkins uses a hack to inject JDK 7 as a tool while > > > the > > > build JVM is Java 8) > > > > > > Should we drop Maven 3.0.5 builds and JDK 7? > > > Notice I didn't check which is the minimum Maven version required... > > > > > > Or perhaps simply don't use the Jenkins Maven plugin with this Maven > > > > 3.0.5 > > > > > or > > > JDK 7 configuration: default build as Jenkins Maven plugin with JDK 8 + > > > latest > > > Maven, and other configurations as scripted jobs? > > > > http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-> > > > type-considered-evil.html > > <http://javaadventure.blogspot.ie/2013/11/jenkins-> > > > maven-job-type-considered-evil.html?m=1> > > > > We should stop using the evil job type as it’s minimum Java version is > > dictated by Jenkins’ Java minimum. > > > > > We need to define our common strategy and have a consistent > > > configuration > > > for > > > every job understood by everybody > > > > I recommend Jenkinsfile and the `withMaven` wrapper > > > > > Regards, > > > > > > Hervé > > > > > > [1] https://builds.apache.org/view/M-R/view/Maven/ > > > > > > [2] > > > https://builds.apache.org/view/M-R/view/Maven/job/maven-> > > > plugin-tools-jdk-1.7/162/console > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > -- > > > > Sent from my phone --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
