[JENKINS-67400] CopyArtifacts fails with relative paths

[jenkins-infra-bot]

---

Originally reported by gordin, imported from: CopyArtifacts fails with relative paths

• assignee: markreiche
• status: Open
• priority: Major
• component(s): copyartifact-plugin
• resolution: Unresolved
• votes: 0
• watchers: 2
• imported: 20260107-133739

environment

Jenkins 2.303.3<br/>
Copy Artifact Plugin 1.46.2

[jenkins-infra-bot]

markreiche:

• Original comment link
• Raw content of original comment:

  I analyzed the issue. The reason for the odd behavior is that the runtime code will only accept a relative path if it is the shortest possible relative path between source project and target project.
  
  In your examples, both projects reside in the same folder, and therefore the relative path specification without any folders will work.
  
  If you had the following jobs:
  
  	
  /folder/CreateArtifacts
  	
  /CopyArtifacts1
  	
  /anotherFolder/CopyArtifacts2
  
  
  
  You could specify the permissions as
  
  	
  ../CopyArtifacts1
  	
  ../anotherFolder/CopyArtifacts2
  
  
  
  (or as absolute paths)
  
  The reason why the validator supports your specs is that it works the other way around: it asks Jenkins if there is some job matching the pattern (and Jenkins seems to do a more sophisticated resolution). This however cannot directly be reused because it only checks whether some/any job matches, but at runtime we need to know if that particular job does.
  
  I think it should not be too hard to fix that issue, but only the other hand I would consider it only a low one, as there is some valid/working relative spec.
  

I analyzed the issue. The reason for the odd behavior is that the runtime code will only accept a relative path if it is the shortest possible relative path between source project and target project.

In your examples, both projects reside in the same folder, and therefore the relative path specification without any folders will work.

If you had the following jobs:

• /folder/CreateArtifacts
• /CopyArtifacts1
• /anotherFolder/CopyArtifacts2

You could specify the permissions as

• ../CopyArtifacts1
• ../anotherFolder/CopyArtifacts2

(or as absolute paths)

The reason why the validator supports your specs is that it works the other way around: it asks Jenkins if there is some job matching the pattern (and Jenkins seems to do a more sophisticated resolution). This however cannot directly be reused because it only checks whether some/any job matches, but at runtime we need to know if that particular job does.

I think it should not be too hard to fix that issue, but only the other hand I would consider it only a low one, as there is some valid/working relative spec.