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

Easy to way to copy workspace files

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Major Major
    • pipeline
    • None

      Frequently it is necessary to copy all or part of a workspace from one node to another within a flow. Doing so using archive and unarchive is possible, but clumsy, and leaves unwanted archives in the build record.

          [JENKINS-26942] Easy to way to copy workspace files

          Jesse Glick created issue -

          Jesse Glick added a comment -

          An alternative/complement to JENKINS-26100.

          Jesse Glick added a comment - An alternative/complement to JENKINS-26100 .
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-26100 [ JENKINS-26100 ]
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-26134 [ JENKINS-26134 ]

          Jesse Glick added a comment -

          Unclear how to do this well, since ArtifactManager does not support deleting a single artifact at the end of a build, so it would be necessary to bypass it and use raw copies to some location in the build directory.

          Jesse Glick added a comment - Unclear how to do this well, since ArtifactManager does not support deleting a single artifact at the end of a build, so it would be necessary to bypass it and use raw copies to some location in the build directory.

          Ing. Christoph Obexer added a comment -

          The usecase I have that I would like to use this for is copying the Testsuite around:

          I don't want it to be archived with the build on the Jenkins master as that would use up a lot of space over time.
          I don't want to use a git step on all the CI slaves (about 30 currently) because I am not allowed to have the source of the application on those machines.

          I want to archive a set of files, give the set a name and be able to unarchive the set of files on any node within the workflow. After the flow execution the archives should be gone. (Maybe a different name for that step would be good like tar or pack or something similar)

          (reposting due to being affected by the data loss; not sure if the comment above is a response to this)

          Ing. Christoph Obexer added a comment - The usecase I have that I would like to use this for is copying the Testsuite around: I don't want it to be archived with the build on the Jenkins master as that would use up a lot of space over time. I don't want to use a git step on all the CI slaves (about 30 currently) because I am not allowed to have the source of the application on those machines. I want to archive a set of files, give the set a name and be able to unarchive the set of files on any node within the workflow. After the flow execution the archives should be gone. (Maybe a different name for that step would be good like tar or pack or something similar) (reposting due to being affected by the data loss; not sure if the comment above is a response to this)
          Jesse Glick made changes -
          Link New: This issue is duplicated by JENKINS-30024 [ JENKINS-30024 ]
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-30025 [ JENKINS-30025 ]
          Jesse Glick made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Jesse Glick made changes -
          Remote Link New: This issue links to "PR 186 (Web Link)" [ 13123 ]

            jglick Jesse Glick
            jglick Jesse Glick
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: