• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Component/s: pipeline-maven-plugin
• Labels:

  None
• Environment:

  jenkins-war:2.187
  Pipeline Maven Integration Plugin:3.8.0

1. 

   screenshot-1.png

   19 kB

   2019-08-16 13:10

[JENKINS-58807] Maven Linker Publisher unable to publish links

Collapse comment: Cyrille Le Clerc added a comment - 2019-08-16 12:10, Edited by Cyrille Le Clerc - 2019-08-16 12:11

Cyrille Le Clerc added a comment - 2019-08-16 12:10 - edited

I have clarified the documentation Pipeline+Maven+Plugin 

You need to also enable the `pipelineGraphPublisher`:

• `pipelineGraphPublisher()` will update the graph of dependencies between Jenkins pipelines and Maven artifacts (produced and dependencies)
• `mavenLinkerPublisher()` will display the Maven details on the Jenkins pipeline build page

Can you try the following:

withMaven(
   publisherStrategy: 'EXPLICIT', 
   options: [pipelineGraphPublisher(), mavenLinkerPublisher()]) {

   sh 'mvn clean deploy'
}
 

 

Expand comment: Cyrille Le Clerc added a comment - 2019-08-16 12:10, Edited by Cyrille Le Clerc - 2019-08-16 12:11

Cyrille Le Clerc added a comment - 2019-08-16 12:10 - edited I have clarified the documentation  Pipeline+Maven+Plugin   You need to also enable the `pipelineGraphPublisher`: `pipelineGraphPublisher()` will update the graph of dependencies between Jenkins pipelines and Maven artifacts (produced and dependencies) `mavenLinkerPublisher()` will display the Maven details on the Jenkins pipeline build page Can you try the following: withMaven( publisherStrategy: 'EXPLICIT' , options: [pipelineGraphPublisher(), mavenLinkerPublisher()]) { sh 'mvn clean deploy' }  

Collapse comment: Lasse Lindqvist added a comment - 2019-08-16 13:15, Edited by Lasse Lindqvist - 2019-08-17 04:35

Lasse Lindqvist added a comment - 2019-08-16 13:15 - edited

Thanks. I tried that, and it does what I was hoping for

Maybe the pom file could also be linked, since some parent artifacts are plain poms, but it is fine as it is too.

As a bit unrelated issue, the "https://" from the beginning of the links is stripped away. This breaks links if the Artifactory only allows explicit https://artifactory... address.

 

Edit:

The pom decision seems to be on purpose here: https://github.com/jenkinsci/pipeline-maven-plugin/blob/pipeline-maven-3.8.1/jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/util/XmlUtils.java#L464

For the stripped https I couldn't find an explanation from this plugin, so it is most likely from somewhere else.

Expand comment: Lasse Lindqvist added a comment - 2019-08-16 13:15, Edited by Lasse Lindqvist - 2019-08-17 04:35

Lasse Lindqvist added a comment - 2019-08-16 13:15 - edited Thanks. I tried that, and it does what I was hoping for Maybe the pom file could also be linked, since some parent artifacts are plain poms, but it is fine as it is too. As a bit unrelated issue, the "https://" from the beginning of the links is stripped away. This breaks links if the Artifactory only allows explicit https://artifactory... address.   Edit: The pom decision seems to be on purpose here: https://github.com/jenkinsci/pipeline-maven-plugin/blob/pipeline-maven-3.8.1/jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/util/XmlUtils.java#L464 For the stripped https I couldn't find an explanation from this plugin, so it is most likely from somewhere else.