On Sat, Oct 25, 2014 at 8:57 AM, Nigel Magnay <nigel.mag...@gmail.com> wrote: > Being able to really cheaply push entire workspaces around feels like a > worthwhile improvement
Yes. Probably the API should also cover interactive workspace browsing; I think https://issues.jenkins-ci.org/browse/JENKINS-25224 is sufficiently related that they should be investigated together. Another use case would be EC2 slaves using EBS. If the slave is configured to take a snapshot of the workspace before exiting, another slave (or several concurrently) could cheaply create new volumes based on that snapshot. And the Jenkins master could permit workspace browsing long after the build is complete and the slaves have been discarded, by reserving a single EC2 machine which just attaches volumes for workspace snapshots on demand and serves content from them. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
