|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-14637) Maven Deployment Linker do... [email protected] (JIRA)
- [JIRA] (JENKINS-14637) Maven Deployment Link... [email protected] (JIRA)
- [JIRA] (JENKINS-14637) Maven Deployment Link... [email protected] (JIRA)
- [JIRA] (JENKINS-14637) Maven Deployment Link... [email protected] (JIRA)
- [JIRA] (JENKINS-14637) Maven Deployment Link... [email protected] (JIRA)

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