• Type: Bug
• Resolution: Fixed
• Priority: Major
• Component/s: copyartifact-plugin
• Labels:

  None
• Environment:

  Ubuntu 14.04 x86_64
  Oracle JDK 1.7
  Jenkins ver. 1.642.1
  Copy Artifact Plugin ver 1.37
  CloudBees Folders Plugin ver 5.1
  

1. System Information [Jenkins].htm

   40 kB

   2016-03-03 04:09

2. Update Center - installed plugins [Jenkins].html

   161 kB

   2016-03-03 04:01

3. 

   screenshot-2.png

   20 kB

   2016-03-01 23:53

4. 

   screenshot-1.png

   23 kB

   2016-03-01 23:53

[JENKINS-33257] "Unable to find project" in "Permission to Copy Artifact - Projects to allow copy artifacts" with multi-configuration projects

Rick Liu created issue - 2016-03-01 23:40

Rick Liu made changes - 2016-03-01 23:42

Description

Original: Related to: JENKINS-14999 To use input parameter variable in "*+project name+*" of "*+copy artifacts from another project+*", you must set proper read permission at upstream job. At upstream job while working together with *+CloudBees Folders Plugin+*, "*+Permission to Copy Artifact - Projects to allow copy artifacts+*" display a misleading warning "{color:red}*+Unable to find project: DOWNSTREAM_PROJECT_NAME+*{color}" when using DOWNSTREAM_PROJECT_NAME only without "FOLDERNAME" prefix. When using full complete name together with FOLDER_NAME, such as "*+FOLDERNAME/DOWNSTREAM_PROJECT_NAME+*", "*+Permission to Copy Artifact - Projects to allow copy artifacts+*" will not display warning. However, the downstream job is unable to copy artifacts with error: {code:bash} ERROR: Unable to find project for artifact copy: FOLDER_NAME/DOWNSTREAM_PROJECT_NAME This may be due to incorrect project name or permission settings; see help for project name in job configuration. {code}

New: Related to: JENKINS-14999 To use input parameter variable in "*+project name+*" of "*+copy artifacts from another project+*", you must set proper read permission at upstream job. At upstream job while working together with *+CloudBees Folders Plugin+*, "*+Permission to Copy Artifact - Projects to allow copy artifacts+*" display a misleading warning "{color:red}*+Unable to find project: DOWNSTREAM_PROJECT_NAME+*{color}" when using DOWNSTREAM_PROJECT_NAME only without "FOLDERNAME" prefix. When using full complete name together with FOLDER_NAME, such as "*+FOLDERNAME/DOWNSTREAM_PROJECT_NAME+*", "*+Permission to Copy Artifact - Projects to allow copy artifacts+*" will not display warning. However, the downstream job is unable to copy artifacts with error: {code:none} ERROR: Unable to find project for artifact copy: FOLDER_NAME/DOWNSTREAM_PROJECT_NAME This may be due to incorrect project name or permission settings; see help for project name in job configuration. {code}

Rick Liu made changes - 2016-03-01 23:43

Description

Original: Related to: JENKINS-14999 To use input parameter variable in "*+project name+*" of "*+copy artifacts from another project+*", you must set proper read permission at upstream job. At upstream job while working together with *+CloudBees Folders Plugin+*, "*+Permission to Copy Artifact - Projects to allow copy artifacts+*" display a misleading warning "{color:red}*+Unable to find project: DOWNSTREAM_PROJECT_NAME+*{color}" when using DOWNSTREAM_PROJECT_NAME only without "FOLDERNAME" prefix. When using full complete name together with FOLDER_NAME, such as "*+FOLDERNAME/DOWNSTREAM_PROJECT_NAME+*", "*+Permission to Copy Artifact - Projects to allow copy artifacts+*" will not display warning. However, the downstream job is unable to copy artifacts with error: {code:none} ERROR: Unable to find project for artifact copy: FOLDER_NAME/DOWNSTREAM_PROJECT_NAME This may be due to incorrect project name or permission settings; see help for project name in job configuration. {code}

New: Related to: JENKINS-14999 To use input parameter variable in "*+project name+*" of "*+copy artifacts from another project+*", you must set proper read permission at upstream job. At upstream job while working together with *+CloudBees Folders Plugin+*, "*+Permission to Copy Artifact - Projects to allow copy artifacts+*" display a misleading warning "{color:red}*+Unable to find project: DOWNSTREAM_PROJECT_NAME+*{color}" when using DOWNSTREAM_PROJECT_NAME only without "FOLDERNAME" prefix. When using full complete name together with FOLDER_NAME, such as "*+FOLDERNAME/DOWNSTREAM_PROJECT_NAME+*", "*+Permission to Copy Artifact - Projects to allow copy artifacts+*" will not display warning. However, the downstream job is unable to copy artifacts with error: {code:none} ERROR: Unable to find project for artifact copy: FOLDER_NAME/DOWNSTREAM_PROJECT_NAME This may be due to incorrect project name or permission settings; see help for project name in job configuration. {code} If it's intended to use PROJECT_NAME only without full-name to include FOLDER_NAME, then it should not display this misleading warning. Also this note should put together with HELP string.

Rick Liu made changes - 2016-03-01 23:53

Attachment

New: screenshot-1.png [ 32075 ]

Rick Liu made changes - 2016-03-01 23:53

Attachment

New: screenshot-2.png [ 32076 ]

Rick Liu made changes - 2016-03-03 04:01

Attachment

New: Update Center - installed plugins [Jenkins].html [ 32086 ]

Rick Liu made changes - 2016-03-03 04:09

Attachment

New: System Information [Jenkins].htm [ 32087 ]

ikedam made changes - 2016-03-03 23:07

Assignee		New: ikedam [ ikedam ]
Summary	Original: Misleading warning "Unable to find project" in "Permission to Copy Artifact - Projects to allow copy artifacts"	New: "Unable to find project" in "Permission to Copy Artifact - Projects to allow copy artifacts" with multi-configuration projects

ikedam made changes - 2016-03-21 07:51

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

SCM/JIRA link daemon made changes - 2016-04-01 23:47

Resolution		New: Fixed [ 1 ]
Status	Original: In Progress [ 3 ]	New: Resolved [ 5 ]

ikedam made changes - 2016-04-17 01:19

Status

Original: Resolved [ 5 ]

New: Closed [ 6 ]

Load more newer history items