[
https://issues.jenkins-ci.org/browse/JENKINS-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162844#comment-162844
]
Brian Murrell edited comment on JENKINS-10313 at 5/16/12 7:36 PM:
------------------------------------------------------------------
How can this be Resolved/Not A Defect? I'm going to Reopen for further
discussion.
Requiring any project that will be the source of a Copy Artifacts action to
have to be readable even by all authenticated users eliminates any use one can
get out of individual or group ACLs and reduces the effective security model to
only two groups of people, authenticated and non-authenticated.
i.e. I cannot create a project that is readable by only some authenticated
users.
The solution, it seems to me (a layperson in terms of any knowledge of the
architecture of Jenkins) is that this plugin should be run with the permissions
of the user initiating the job that the plugin is being used in thus one can
assign read permission to people expected to be able to read the artifacts in
one's ACLs.
was (Author: brian):
How can this be Resolved/Not A Defect? I'm going to Reopen for further
discussion.
Requiring any project that will be the source of a Copy Artifacts action to
have to be readable even by all authenticated users eliminates any use one can
get out of individual or group ACLs and reduces the effective security model to
only two groups of people, authenticated and non-authenticated.
i.e. I cannot create a project that is readable by only some authenticated
users.
The solution, it seems to me (a layperson in terms of any knowledge of the
architecture of Jenkins) is that this plugin should be represented by a
particular authenticated user that one can assign read permission to in one's
ACLs.
> Fails to copy artifacts from one multi-configuration build to another
> ---------------------------------------------------------------------
>
> Key: JENKINS-10313
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10313
> Project: Jenkins
> Issue Type: Bug
> Components: copyartifact
> Affects Versions: current
> Environment: Mac OS X 10.6.8 client running Jenkins Master
> Ubuntu 10.04 running Jenkins slave
> Copy Artifact Plugin v1.16
> Jenkins v1.420
> Reporter: snrkiwi71
> Assignee: Alan Harder
>
> [can't find anything on this in the issues tracker, nor the 'net]
> Project A ("ztest1") is a multi-configuration job that produces artifacts for
> Ubuntu and Mac OS X (axes values = macosx64, ubuntuLynx32), for two fake
> branches (axes values = x, y). Project B ("ztest2") wants access to the
> appropriate artifacts from A, given the OS/branch combination.
> Using "ztest1/label=macosx64,branch=x" as the "Project name" for copy
> artifacts works, for all B combinations, but this obviously copies the
> artifacts for macosx64/x into all B combinations.
> Using "ztest1/label=$label,branch=x" instead produces the following error.
> {{Unable to find project for artifact copy: ztest1/label=macosx64,branch=x
> This may be due to incorrect project name or permission settings; see help
> for project name in job configuration.
> Build step 'Copy artifacts from another project' marked build as failure}}
> The actual project name, including the parameters, is correct, but it fails.
> The same happens if you use "...,branch=$branch" also.
> The copy artifacts help instructs
> {{To copy artifacts from one matrix project to another, use a parameter to
> select the matching configuration in the source project. Example:
> OtherMatrixJob/jdk=$jdk}}
> so I believe that the above syntax is correct.
> The Hudson log for failed B build shows only
> {{Jul 12, 2011 12:16:43 PM hudson.model.Run run
> INFO: ztest2 #12 main build action completed: FAILURE
> Jul 12, 2011 12:16:42 PM hudson.model.Run run
> INFO: ztest2 » x,macosx64 #12 main build action completed: FAILURE
> Jul 12, 2011 12:16:33 PM hudson.model.Run run
> INFO: ztest2 #11 main build action completed: FAILURE
> Jul 12, 2011 12:16:32 PM hudson.model.Run run
> INFO: ztest2 » x,macosx64 #11 main build action completed: FAILURE
> Jul 12, 2011 12:13:06 PM hudson.model.Run run
> INFO: ztest2 #10 main build action completed: FAILURE}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
