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

Allow separate deploy and publish locations for artifact deployer

    Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      Jenkins master: unix
      Jenkins build nodes: mixed Windows/Unix
      Artifacts archived on a NAS
    • Similar Issues:

      Description

      We have a heterogeneous Windows/Unix build infrastructure. We'd like to archive build results and have users download from the Jenkins master, but we want the artifacts to actually be archived on a NAS.

      If we use a unix-style path as the remote file location, this gets translated to e.g. d:\path\to\archive\file.zip and the download link doesn't work. UNC paths don't work either.

      Allowing separate push-to and publish-from locations in the configuration would fix this for us. We could use a UNC path to a Samba share for the Windows build node and the corresponding NFS path for Jenkins to link against on the webpage.

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              gbois Gregory Boissinot
              Reporter:
              wsaxon Will Saxon
            • Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: