Title: Message Title
Sam Liddicott commented on JENKINS-33003
Re: Copy Artifacts from Another Projects Strange Behavior
Not only must you specify the upstream job, you must specify it as a literal you you can't even prepare a groovy environment that computes the value. If a variable is used, the copy fails with a message indicating the actual name that it ought to have been able to copy and can copy if specified literally 07:10:26 ERROR: Unable to find project for artifact copy: blah/thingy-project 07:10:26 This may be due to incorrect project name or permission settings; see help for project name in job configuration.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.