|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I would very much like this same functionality. I'm looking at using ArtifactDeployer instead of the internal code - to allow easily archiving artifacts to a separate file server not part of the jenkins build agent host - but would hate to lose the functionality of being able to refer/copy those artifacts in other builds.
I realize I could copy explicit file paths, or I could rig up something like an extra publish action - to publish to both a "by build number" as well as "last successful" directory, but that seems a bit hackish.
Suggestions?