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

Artifactory upload failing when Jenkins job is in a folder

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • artifactory-plugin
    • None

      Jenkins jobs located in folders fail uploading files with the generic Artifactory uploader. I get the following error:

      2017-02-09 16:11:48,812 [http-nio-8081-exec-9366] [WARN ] (o.a.r.ArtifactoryResponseBase:107) - Sending HTTP error code 409: Old metadata notation is not supported anymore: div08-edp:BuildCloud/SIM4000/T0.1.0.69/libGeo.a;build.parentNumber=69;vcs.revision=124440;build.parentName=Control+::+SIM_RL;build.timestamp=1486646016375;build.name=Control+::+SIM_RL_FWPACKAGE;build.number=69
      

      The same artifact uploads fine when I move the Jenkins job out of the folder into the root level. I think the problem might be caused by the plus signs or the colons.

          [JENKINS-41898] Artifactory upload failing when Jenkins job is in a folder

          Johannes Asal added a comment -

          I just found that overriding the build name is a temporary workaround.

          Johannes Asal added a comment - I just found that overriding the build name is a temporary workaround.

          Johannes Asal added a comment -

          The workaround doesn't work for Multiconf projects because then the plugin adds more attributes to the upload (build.parentName, build.number) that also contain the plus signs and colons and which I can't override.

          Johannes Asal added a comment - The workaround doesn't work for Multiconf projects because then the plugin adds more attributes to the upload (build.parentName, build.number) that also contain the plus signs and colons and which I can't override.

            eyalbe Eyal Ben Moshe
            jasal Johannes Asal
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: