Go on then I'll bite... If we had a useable alternative then we may not all be using it...
this includes (of the top of my head) * knowing what is installed (by maven) so that it (can be optionally) automatically added as an archive. * plugins that don’t fail the build when the foobar.xml they require doesn’t exist (as this build has no checkstyle as it is building an RPM) * Knowing where foobar.xml report is created… (not all checkstyle.xml are reports from the project that we want the plugin to scan!) Managing 600+ jobs an having to keep a list of "artifacts to archive" in sync for all of these stuff (wildcards don’t work due to the nature of maven, the projects using it etc..) is not a viable option and would need a dedicated team of people to manage just the job configuration alone! Provide us with a viable alternative and people will use it J Hasn't Sacha signed off on you doing this work for Jenkins Enterprise yet! Or actually I guess this is a Maven job type but one that only intercepts stuff and doesn’t mess with anything (changing the mojo config on the fly…) /James On Monday, 29 April 2013 09:36:30 UTC+1, Stephen Connolly wrote: > > Turns out this is actually a rather nasty bug in Jenkins' Maven project > type... which had been masked by some settings.xml magic that we were > applying but shouldn't have been applying > > [image: Inline images 1] > > And where is the problem? > > Well install:install is running.... and oh look Jenkins has mucked about > via its evil Maven job type > > Caused by: java.lang.IllegalStateException: Failed to build parent project > for org.jenkins-ci.plugins:jswidgets:hpi:1.10-SNAPSHOT > at > org.apache.maven.project.MavenProject.getParent(MavenProject.java:378) > at > hudson.maven.reporters.MavenFingerprinter.recordParents(MavenFingerprinter.java:141) > at > hudson.maven.reporters.MavenFingerprinter.postBuild(MavenFingerprinter.java:110) > > > So basically the Maven job type is trying to resolve the parents of the > files it fingerprints and because it doesn't know the repositories it blows > up and kills a perfectly fine build. > > Freestyle + Maven build step would never do this to you! > > Been saying that its evil for 6+ years now... > > ;-) > > > On 26 April 2013 21:34, Jesse Glick <[email protected] <javascript:>>wrote: > >> On Fri, Apr 26, 2013 at 4:03 PM, Mirko Friedenhagen >> <[email protected] <javascript:>> wrote: >> > the job is trying to get maven-hpi-plugin-1.74 from central and fails >> because of this >> >> Yes a bunch of BuildHive jobs for Jenkins plugins got broken recently >> due to a change in Maven mirror handling. We are working on >> determining the real cause and how to fix it. >> >> -- >> 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:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
