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

19 views
Skip to first unread message

lasse.k.lindqvist@gmail.com (JIRA)

unread,
Aug 5, 2019, 6:45:02 AM8/5/19
to jenkinsc...@googlegroups.com
Lasse Lindqvist created an issue
 
Jenkins / New Feature JENKINS-58807
Maven Linker Publisher unable to publish links
Issue Type: New Feature New Feature
Assignee: Alvaro Lobato
Components: pipeline-maven-plugin
Created: 2019-08-05 10:44
Environment: jenkins-war:2.187
Pipeline Maven Integration Plugin:3.8.0
Priority: Minor Minor
Reporter: Lasse Lindqvist

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.
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

lasse.k.lindqvist@gmail.com (JIRA)

unread,
Aug 5, 2019, 6:49:01 AM8/5/19
to jenkinsc...@googlegroups.com
Lasse Lindqvist updated an issue
Change By: Lasse Lindqvist
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'
     }

cleclerc@cloudbees.com (JIRA)

unread,
Aug 16, 2019, 8:07:02 AM8/16/19
to jenkinsc...@googlegroups.com
Cyrille Le Clerc updated an issue
Change By: Cyrille Le Clerc
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( maven publisherStrategy : ' M3 EXPLICIT ',
     options: [mavenLinkerPublisher()] ,
     publisherStrategy: 'EXPLICIT' ) {
      sh 'mvn clean deploy'
     }


{code}
 

cleclerc@cloudbees.com (JIRA)

unread,
Aug 16, 2019, 8:11:03 AM8/16/19
to jenkinsc...@googlegroups.com
Cyrille Le Clerc commented on New Feature JENKINS-58807
 
Re: Maven Linker Publisher unable to publish links

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'}

cleclerc@cloudbees.com (JIRA)

unread,
Aug 16, 2019, 8:11:03 AM8/16/19
to jenkinsc...@googlegroups.com
Cyrille Le Clerc assigned an issue to Cyrille Le Clerc
 
Change By: Cyrille Le Clerc
Assignee: Alvaro Lobato Cyrille Le Clerc

cleclerc@cloudbees.com (JIRA)

unread,
Aug 16, 2019, 8:11:03 AM8/16/19
to jenkinsc...@googlegroups.com
Cyrille Le Clerc updated an issue
Change By: Cyrille Le Clerc
Issue Type: New Feature Bug

cleclerc@cloudbees.com (JIRA)

unread,
Aug 16, 2019, 8:12:01 AM8/16/19
to jenkinsc...@googlegroups.com
Cyrille Le Clerc edited a comment on Bug JENKINS-58807


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:
{code:java}
 withMaven(
publisherStrategy: 'EXPLICIT',
options: [pipelineGraphPublisher(), mavenLinkerPublisher()]) {
   sh 'mvn clean deploy'
}

{code}
 

cleclerc@cloudbees.com (JIRA)

unread,
Aug 16, 2019, 8:12:02 AM8/16/19
to jenkinsc...@googlegroups.com
Cyrille Le Clerc started work on Bug JENKINS-58807
 
Change By: Cyrille Le Clerc
Status: Open In Progress

lasse.k.lindqvist@gmail.com (JIRA)

unread,
Aug 16, 2019, 9:11:01 AM8/16/19
to jenkinsc...@googlegroups.com
Lasse Lindqvist updated an issue
 
Change By: Lasse Lindqvist
Attachment: screenshot-1.png

lasse.k.lindqvist@gmail.com (JIRA)

unread,
Aug 16, 2019, 9:16:02 AM8/16/19
to jenkinsc...@googlegroups.com
Lasse Lindqvist commented on Bug JENKINS-58807
 
Re: Maven Linker Publisher unable to publish links

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.

lasse.k.lindqvist@gmail.com (JIRA)

unread,
Aug 17, 2019, 12:34:03 AM8/17/19
to jenkinsc...@googlegroups.com
Lasse Lindqvist edited a comment on Bug JENKINS-58807
Thanks. I tried that, and it does what I was hoping for
!screenshot-1.png|thumbnail!


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...|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

lasse.k.lindqvist@gmail.com (JIRA)

unread,
Aug 17, 2019, 12:36:01 AM8/17/19
to jenkinsc...@googlegroups.com
Lasse Lindqvist edited a comment on Bug JENKINS-58807
Thanks. I tried that, and it does what I was hoping for
!screenshot-1.png|thumbnail!

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...|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.
Reply all
Reply to author
Forward
0 new messages