Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-58807

Maven Linker Publisher unable to publish links

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • pipeline-maven-plugin
    • None
    • jenkins-war:2.187
      Pipeline Maven Integration Plugin:3.8.0

      When enabling Maven Linker Publisher, the pipeline syntax generator suggests "Don't forget to enable the "Downstream Pipeline Triggers" publisher to enable the "Maven Linker" publisher."

      As the instructions imply, just using the Linker Publisher does nothing, but there is no "Downstream Pipeline Triggers" that can be enabled.
      Only Pipeline Graph Publisher has such a choice, and it doesn't seem clear how it should be used to be able to do only link publishing.

      Example pipeline syntax which does not publish links:

      withMaven(publisherStrategy: 'EXPLICIT', options: [mavenLinkerPublisher()]) {
   sh 'mvn clean deploy'
}

       

        1. screenshot-1.png
          screenshot-1.png
          19 kB

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

          Lasse Lindqvist created issue -
          Lasse Lindqvist made changes -
          Description Original: When enabling Maven Linker Publisher, the pipeline syntax generator suggests "Don't forget to enable the "Downstream Pipeline Triggers" publisher to enable the "Maven Linker" publisher."

          As the instructions imply, just using the Linker Publisher does nothing, but there is no "Downstream Pipeline Triggers" that can be enabled.
          Only Pipeline Graph Publisher has such a choice, and it doesn't seem clear how it should be used to be able to do only link publishing.           		New: When enabling Maven Linker Publisher, the pipeline syntax generator suggests "Don't forget to enable the "Downstream Pipeline Triggers" publisher to enable the "Maven Linker" publisher."

          As the instructions imply, just using the Linker Publisher does nothing, but there is no "Downstream Pipeline Triggers" that can be enabled.
          Only Pipeline Graph Publisher has such a choice, and it doesn't seem clear how it should be used to be able to do only link publishing.

          Example pipeline syntax which does not publish links:
          withMaven(maven: 'M3',
          options: [mavenLinkerPublisher()],
          publisherStrategy: 'EXPLICIT') {
          sh 'mvn clean deploy'
          }
          Cyrille Le Clerc made changes -
          Description Original: When enabling Maven Linker Publisher, the pipeline syntax generator suggests "Don't forget to enable the "Downstream Pipeline Triggers" publisher to enable the "Maven Linker" publisher."

          As the instructions imply, just using the Linker Publisher does nothing, but there is no "Downstream Pipeline Triggers" that can be enabled.
          Only Pipeline Graph Publisher has such a choice, and it doesn't seem clear how it should be used to be able to do only link publishing.

          Example pipeline syntax which does not publish links:
          withMaven(maven: 'M3',
          options: [mavenLinkerPublisher()],
          publisherStrategy: 'EXPLICIT') {
          sh 'mvn clean deploy'
          }           		New: When enabling Maven Linker Publisher, the pipeline syntax generator suggests "Don't forget to enable the "Downstream Pipeline Triggers" publisher to enable the "Maven Linker" publisher."

          As the instructions imply, just using the Linker Publisher does nothing, but there is no "Downstream Pipeline Triggers" that can be enabled.
           Only Pipeline Graph Publisher has such a choice, and it doesn't seem clear how it should be used to be able to do only link publishing.

          Example pipeline syntax which does not publish links:
          {code:java}
          withMaven(publisherStrategy: 'EXPLICIT', options: [mavenLinkerPublisher()]) {
             sh 'mvn clean deploy'
          }

          {code}
           

          Cyrille Le Clerc added a comment - - 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'
}

           

          Cyrille Le Clerc added a comment - - 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' }  
          Cyrille Le Clerc made changes -
          Assignee Original: Alvaro Lobato [ alobato ] New: Cyrille Le Clerc [ cleclerc ]
          Cyrille Le Clerc made changes -
          Issue Type Original: New Feature [ 2 ] New: Bug [ 1 ]
          Cyrille Le Clerc made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Lasse Lindqvist made changes -
          Attachment New: screenshot-1.png [ 48343 ]

          Lasse Lindqvist added a comment - - 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.

          Lasse Lindqvist added a comment - - 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.
          Arnaud Héritier made changes -
          Assignee Original: Cyrille Le Clerc [ cleclerc ]

            Unassigned Unassigned
            lasselindqvist Lasse Lindqvist
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: