[JIRA] [copyartifact] (JENKINS-22002) Copy Artifact doesn't support jobs in different Folders
ikedam resolved JENKINS-22002 as Not A Defect Copy Artifact doesnt support jobs in different Folders It was a permission issue. I also updated wiki page adding instructions for permission configuration (JENKINS-21821). Change By: ikedam (20/Mar/14 10:55 AM) Status: Open Resolved Resolution: NotADefect 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-22002) Copy Artifact doesn't support jobs in different Folders
Walter Kacynski closed JENKINS-22002 as Not A Defect Copy Artifact doesnt support jobs in different Folders Thank-You, the wiki documentation updates make sense now. Change By: Walter Kacynski (20/Mar/14 11:58 AM) Status: Resolved Closed 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-22002) Copy Artifact doesn't support jobs in different Folders
Walter Kacynski commented on JENKINS-22002 Copy Artifact doesnt support jobs in different Folders I could not get the relative paths to work, however using * did work. * is fine for me since these builds don't need to be secured for other users. I don't really understand why this security is required if the user who triggered the build has authority to both the upstream and downstream jobs. Are you checking the build causer for security? For triggering there are two causers (trigger and user). 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-22002) Copy Artifact doesn't support jobs in different Folders
ikedam commented on JENKINS-22002 Copy Artifact doesnt support jobs in different Folders 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. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-22002) Copy Artifact doesn't support jobs in different Folders
ikedam commented on JENKINS-22002 Copy Artifact doesnt support jobs in different Folders JIRA was down and @walterk82 sent me a mail: *Yes, we have Jenkins security enabled. *No, variables have never worked for me. I did Option 3 "Specify jobs who can copy artifacts in the configuration page of the job with artifacts" but I'm still seeing the same behavior. The upstream and downstream jobs can be read and submitted by the same user. I am a global Jenkins administrator so there should be no security problems here. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-22002) Copy Artifact doesn't support jobs in different Folders
ikedam commented on JENKINS-22002 Copy Artifact doesnt support jobs in different Folders I found that "Permission to Copy Artifact" works only for relative job names: When /folder1/copier copies artifacts from /folder2/copiee Projects to allow copy artifacts Result /folder1/copier (absolute) Fail ../folder1/copier (relative) Succeed I will fix this problem in the next release. Would you try followings? Test the behavior specifying the relative name of the upstream job in "Permission to Copy Artifact Projects to allow copy artifacts" of downstream job. (If the former fails) Test the behavior specifying "*" in "Permission to Copy Artifact Projects to allow copy artifacts" of downstream job. (This not a recommended configuration. Only for testing purpose) 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-22002) Copy Artifact doesn't support jobs in different Folders
Walter Kacynski assigned JENKINS-22002 to ikedam Copy Artifact doesnt support jobs in different Folders I think I have all the information attached that you asked for. The problem seems to occurs when we use a job build variable to find the source project to copy from. If we use a hard-coded job path everything works fine. Change By: Walter Kacynski (03/Mar/14 1:43 PM) Assignee: ikedam 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-22002) Copy Artifact doesn't support jobs in different Folders
Walter Kacynski updated JENKINS-22002 Copy Artifact doesnt support jobs in different Folders Change By: Walter Kacynski (03/Mar/14 1:42 PM) Attachment: downstream-config.xml Attachment: OutputWithBuildVariable.png Attachment: OutputWithHardcodedJob.png Attachment: upstream-config.xml 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-22002) Copy Artifact doesn't support jobs in different Folders
ikedam commented on JENKINS-22002 Copy Artifact doesnt support jobs in different Folders As long as I tested, it should work. Please report how to reproduce the problem. Job configurations. Structures of jobs and folders. And "folder" means cloudbees-folder plugin? Artifacts they archive. Copyartifact configurations. Especially, how you specify job names. Absolute/relative, static/dynamic (using variables). Expected result. Actual result. I don't know what is the attached file. If you want a support for your Jenkins Enterprise, you cannot get that here. Please contact cloudbees professional support. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-22002) Copy Artifact doesn't support jobs in different Folders
Walter Kacynski created JENKINS-22002 Copy Artifact doesnt support jobs in different Folders Issue Type: Bug Assignee: Unassigned Attachments: cloudbees-support(1).zip Components: copyartifact Created: 28/Feb/14 7:44 PM Description: When we use copy artifact version 1.30 but it doesn't seem to resolve jobs across different folders. If the source job and target job are within the same folder then we are able to use this plugin correctly. Project: Jenkins Priority: Major Reporter: Walter Kacynski 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
