[JIRA] [mock-slave] (JENKINS-25090) Mock slaves should use a consistent remoteFS after restart

[jgl...@cloudbees.com (JIRA)]

Jesse Glick created JENKINS-25090 Mock slaves should use a consistent remoteFS after restart Issue Type: Bug Assignee: Jesse Glick Components: mock-slave Created: 10/Oct/14 3:00 PM Description: 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. Project: Jenkins Labels: workflow Priority: Major Reporter: Jesse Glick

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.