Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Component/s: copyartifact-plugin
-
Labels:None
-
Similar Issues:
Description
Error message:
... project_name=daily _=/bin/env Unable to find project for artifact copy: daily 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 ...
When I set the project name by hand, there is no error. When I use a build parameter, and set its value to the same value as the hand typed value, it fails. The above message show what variable I use: $project_name
Please see the screenshots for the configuration details.
Attachments
Issue Links
- depends on
-
-
- Resolved
-
- is related to
-
JENKINS-20398 Add a feature to configure projects to allow copy artifacts
-
- Closed
-
-
JENKINS-21821 Write documents to copying permission
-
- Closed
-
Activity
After some further combination of trials,
I found out that "Permission to Copy Artifact - Projects to allow copy artifacts" must set to a project name without FOLDER_NAME.
This resolves the problem too.
However,
there's a misleading warning "Unable to find project:"
when set the upstream job "Permission to Copy Artifact - Projects to allow copy artifacts"
to a DOWNSTREAM_PROJECT_NAME only without FOLDER_NAME.
I'll create a separate JIRA ticket for that.
Rick Liu
added a comment - After some further combination of trials,
I found out that "Permission to Copy Artifact - Projects to allow copy artifacts" must set to a project name without FOLDER_NAME.
This resolves the problem too.
However,
there's a misleading warning "Unable to find project:"
when set the upstream job "Permission to Copy Artifact - Projects to allow copy artifacts"
to a DOWNSTREAM_PROJECT_NAME only without FOLDER_NAME.
I'll create a separate JIRA ticket for that. created JENKINS-33257 for the misleading warning
Rick Liu
added a comment - created JENKINS-33257 for the misleading warning I'm still getting this in 1.3.7 / Jenkins ver. 1.651.1
Jakub Bochenski
added a comment - I'm still getting this in 1.3.7 / Jenkins ver. 1.651.1 
I have this same issue.
Jenkins ver. 1.642.1
Copy Artifact Plugin ver 1.37
CloudBees Folders Plugin ver 5.1
On the upstream trigger job,
I have explicitly set "Permission to Copy Artifact - Projects to allow copy artifacts"
for the full downstream job name including Folder-Plugin's foldername "FOLDNER_NAME/DOWNSTREAM_PROJECT_NAME".
But this still causes the error on the downstream job:
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.
If on the upstream trigger job,
I have explicitly set "Permission to Copy Artifact - Projects to allow copy artifacts"
for the full downstream job name to wildcard '*',
then the problem solved.