|
||||||||
|
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.
It's OK to use * if access control for those artifacts is not so important.
Jenkins is designed to authorize a running build as the system user even it is triggered by a user. This makes things difficult.
This means build authorization is useless as security, and so copyartifact plugin acts as an anonymous user by default to minimize security risks.
Authorize Project plugin provides a feature to authorize a build as a user who triggerd the build, and copyartifact plugin can work well with it. (But I'm not sure it works well for your case as it doesn't work with scheduled builds.)
Could you let me know the details you failed to copy even with relative job names? (project names, and the relative name you specified)
I think your problem is resolved, but I plan to fix and improve "Projects to allow copy artifacts" feature in JENKINS-22038, and I want to know more cases where it does not work well.