Mock slaves should use a consistent remoteFS after restart

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

ExportXMLWordPrintable

      For testing durable tasks you need to have a consistent workspace (so, remoteFS) even after Jenkins is restarted. Currently the remoteFS is random, to avoid conflicts. Should rather be based on the slave name plus the Jenkins instance ID or something like this.

            Assignee:
            Jesse Glick
            Reporter:
            Jesse Glick
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: