Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-67400

CopyArtifacts fails with relative paths

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • copyartifact-plugin
    • None
    • Jenkins 2.303.3
      Copy Artifact Plugin 1.46.2

      When using a relative path in "Permission to Copy Artifact" the other project is not allowed to copy artifacts. Using an absolute path works as expected.

      Consider the following scenario with two jobs

      /folder/CreateArtifacts
      /folder/CopyArtifacts

      Using the following "Permission to Copy Artifact" in CreateArtifacts works as expected

      • *
      • CopyArtifacts
      • /*
      • /folder/*
      • /folder/CopyArtifacts

      But, the following does not work:

      • ./*
      • ./CopyArtifacts
      • ../*
      • ../folder/*
      • ../folder/CopyArtifacts

      Maybe, the first two cases might not work by design (and the exact same behavior can be achieved by using "*" and "CopyArtifacts" respectively).

      But, the other permissions should work. When using a deeper folder-structure this is needed. When using "./CopyArtifacts" and "../folder/CopyArtifacts" no "Unable to find project" warning is shown in the configuration. It seems the validator is able to find the jobs with this path just fine.

            markreiche Mark
            gordin Christoph VogtlÃĪnder
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: