|
||||||||
|
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/d/optout.
Before writing tests, I tested the behavior in my environment (Jenkins 1.590.1 + Copyartifact 1.30, Linux master / slave).
It looks that the problem happens not when copying, but when archiving (that is, in upstream builds).
@tsackett
Can you see file permissions of archived artifacts?
They should be in ${JENKINS_HOME}/jobs/(project name)/builds/(build number)/archive . They look lose permissions when archiving on master.