[JIRA] [copyartifact-plugin] (JENKINS-33003) Copy Artifacts from Another Projects Strange Behavior

[estdrmscrc@gmail.com (JIRA)]

Esteban Vargas updated an issue

Jenkins / JENKINS-33003 Copy Artifacts from Another Projects Strange Behavior Change By: Esteban Vargas Summary: Copy Artifacts from Another Projects  Extrange  Strange  Behavior Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[sam@liddicott.com (JIRA)]

Sam Liddicott commented on JENKINS-33003

Re: Copy Artifacts from Another Projects Strange Behavior Not only must you specify the upstream job, you must specify it as a literal you you can't even prepare a groovy environment that computes the value. If a variable is used, the copy fails with a message indicating the actual name that it ought to have been able to copy and can copy if specified literally 07:10:26 ERROR: Unable to find project for artifact copy: blah/thingy-project  07:10:26 This may be due to incorrect project name or permission settings; see help for project name in job configuration.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[devld@ikedam.jp (JIRA)]

ikedam updated JENKINS-33003

Copyartifact requires upstream am project name explicitly as: For its design. Copyartifact decides the job to copy from, and then search builds. The build selection comes later and cannot affect job decision phase. There can be multiple upstream jobs. A case that there’s a grand parent build, or the job is triggered from multiple upstreams and merged into one build.

Jenkins / JENKINS-33003

Copy Artifacts from Another Projects Strange Behavior

Change By: ikedam Status: Open Fixed but Unreleased Assignee: Esteban Vargas Resolution: Won't Fix

Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)