Hello Will, Fingerprint and reports rendering are things we would like to see in forthcoming releases of this plugin. We hope that the community will help on this kind of feature.
For the moment, we unfortunately have to use the following verbose steps: step([$class: 'ArtifactArchiver', artifacts: 'gameoflife-web/target/*.war']) step([$class: 'WarningsPublisher', consoleParsers: [[parserName: 'Maven']]]) step([$class: 'JUnitResultArchiver', testResults: '**/target/surefire-reports/TEST-*.xml']) step([$class: 'JavadocArchiver', javadocDir: 'gameoflife-core/target/site/apidocs/']) ... Cyrille On Saturday, August 13, 2016 at 1:43:37 AM UTC+2, Will Currie wrote: > > Nice. It seems to non-pipeline/'old-school'/regular jenkins maven build > has support for tracking fingerprints of artefacts used and produced by any > given maven build. I'm taking about the work that seems to be done by > MavenFingerprinter > <https://github.com/jenkinsci/maven-plugin/blob/master/src/main/java/hudson/maven/reporters/MavenFingerprinter.java#L97>. > > If I understand correctly this allows you to see builds upstream and > downstream of any given maven build. > > Any thoughts on how this might fit into the pipeline builds? The pipeline > tutorial shows how to configure fingerprints for build outputs > (**/target/*.jar). It doesn't seem to cover tracking fingerprints for what > it consumes. > > Thanks. > > On Friday, 12 August 2016 02:33:19 UTC+10, Álvaro Lobato wrote: >> >> >> Hello everyone, >> >> I'd like to introduce you to the new Pipeline Maven >> <https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Maven+Plugin> plugin . >> The intention of this plugin is to help using maven from pipeline, setting >> up a maven environment by using a withMaven step. This environment can >> later be called with sh or bat step. >> >> The supported configuration parameters are: >> >> - Maven Installation >> - JDK >> - Maven Settings Config (Config File Provider Plugin) >> - Maven Settings File Path >> - Maven JVM Opts >> - Maven Local Repository >> >> The step can be used used directly on a node or in a docker.inside. >> >> Currently it is in an early stage of development and I've just released >> the first beta version, already available in the update center. >> >> This is the start point for a more feature rich integration between >> pipeline and maven. >> >> You can find more information on the wiki page: Pipeline Maven plugin >> <https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Maven+Plugin> >> >> Thanks >> Alvaro. >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5528fdcb-f9a1-4af5-ad6f-c94fac2e20cf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
