CopyArtifacts fails with relative paths

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      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.

            Assignee:
            Mark
            Reporter:
            Christoph Vogtländer
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: