-
Bug
-
Resolution: Fixed
-
Critical
-
None
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.
- depends on
-
JENKINS-16956 Require authentication for build triggers
-
- 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
-
[JENKINS-14999] Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter
Attachment | New: copy-artifact-shot3.png [ 22402 ] |
Resolution | New: Not A Defect [ 7 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Resolution | Original: Not A Defect [ 7 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
After reading more closely the help, I decided to upload another image, this time showing global project permissions. There is no per-project permissions.