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

Maven Deployment Linker does not support all permalinks types

    XMLWordPrintable

Details

    Description

      It is not possible to get Maven artifacts from a Maven release build using Maven Deployment Linker because only choices are to scan linked artifacts in last / last stable / last successfull and similar builds defined by built-in permalinks. Maven release plugin creates another type of permalink that is not supported.

      I'd like to use it in a downstream build that will get (possibly manually tested) artifacts from release build and deploy them or do some other action related to deployment pipeline. Meanwhile there can be many snapshot builds executed in the upstream build (including one spawned by SCM notification after changeset caused by version update).

      Cf. Copy artifact plugin that allows to select this type (but it is not very helpfull because the only artifact linked by Maven release build is master pom).

      See also https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/lZJMsRxpmVE

      Attachments

        Activity

          lshatzer Larry Shatzer, Jr. added a comment - - edited

          The name "linker" in the plugin name does not mean permlinks, but hyperlinks that it puts in the job page. The m2 release plugin already puts a link to the build that caused the release. It seems like a bug for the m2 release plugin, since this plugin is only to put hyperlinks on the build/job pages. It does this by scanning the log of the build for all artifacts uploaded to a maven repository by means of a regex.

          Also some maven jobs (usually multi-module ones) produce multiple artifacts, so how would it know which one(s) to put in the permalink, if there was one?

          lshatzer Larry Shatzer, Jr. added a comment - - edited The name "linker" in the plugin name does not mean permlinks, but hyperlinks that it puts in the job page. The m2 release plugin already puts a link to the build that caused the release. It seems like a bug for the m2 release plugin, since this plugin is only to put hyperlinks on the build/job pages. It does this by scanning the log of the build for all artifacts uploaded to a maven repository by means of a regex. Also some maven jobs (usually multi-module ones) produce multiple artifacts, so how would it know which one(s) to put in the permalink, if there was one?
          radimk Radim Kubacki added a comment -

          AFAICT the functionality of Maven Deployment Linker is not only to put hyperlinks to build/job pages but it also registers a build step that can be used by a downstream build to get linked artifacts from the another build (upstream) build. This makes it possible to create a pipeline of builds where artifact created by first build will be used in the second (downstream) build.

          My complaint is that this action (hudson/plugins/mavendeploymentlinker/MavenDeploymentDownloader.java) can only by used for builds specified by simple criteria and I cannot ask to get artifacts generated by last release build (last release build can be accessed through a permalink).

          radimk Radim Kubacki added a comment - AFAICT the functionality of Maven Deployment Linker is not only to put hyperlinks to build/job pages but it also registers a build step that can be used by a downstream build to get linked artifacts from the another build (upstream) build. This makes it possible to create a pipeline of builds where artifact created by first build will be used in the second (downstream) build. My complaint is that this action (hudson/plugins/mavendeploymentlinker/MavenDeploymentDownloader.java) can only by used for builds specified by simple criteria and I cannot ask to get artifacts generated by last release build (last release build can be accessed through a permalink).

          Ahhh, that functionality was not added by me, but Dominik Bartholdi (imod). I'll assign it to him to look at.

          lshatzer Larry Shatzer, Jr. added a comment - Ahhh, that functionality was not added by me, but Dominik Bartholdi (imod). I'll assign it to him to look at.

          Code changed in jenkins
          User: imod
          Path:
          src/main/java/hudson/plugins/mavendeploymentlinker/MavenDeploymentDownloader.java
          http://jenkins-ci.org/commit/maven-deployment-linker-plugin/b80b10e246bdc802624265f04a04ec9697e312da
          Log:
          [FIXED JENKINS-14637] if possible, get all permalinks from target project

          Compare: https://github.com/jenkinsci/maven-deployment-linker-plugin/compare/1e3eed66f818...b80b10e246bd


          You received this message because you are subscribed to the Google Groups "Jenkins Commits" group.
          To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscribe@googlegroups.com.
          For more options, visit https://groups.google.com/groups/opt_out.

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: imod Path: src/main/java/hudson/plugins/mavendeploymentlinker/MavenDeploymentDownloader.java http://jenkins-ci.org/commit/maven-deployment-linker-plugin/b80b10e246bdc802624265f04a04ec9697e312da Log: [FIXED JENKINS-14637] if possible, get all permalinks from target project Compare: https://github.com/jenkinsci/maven-deployment-linker-plugin/compare/1e3eed66f818...b80b10e246bd – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out .

          People

            domi Dominik Bartholdi
            radimk Radim Kubacki
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: