Re: Parameterise slaves launched in a cloud [workflow ?]

2014-10-31 Thread Nigel Magnay
I've created a PR to cover this: https://github.com/jenkinsci/jenkins/pull/1448 I think it's relatively sane, though the NodeProvisioner had changed around a bit between me writing it and rebasing to submit the PR. On Sat, Oct 25, 2014 at 5:11 PM, Jesse Glick wrote: > On Sat, Oct 25, 2014 at 8

Re: Parameterise slaves launched in a cloud [workflow ?]

2014-10-25 Thread Jesse Glick
On Sat, Oct 25, 2014 at 8:57 AM, Nigel Magnay 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 sufficient

Re: Parameterise slaves launched in a cloud [workflow ?]

2014-10-25 Thread Nigel Magnay
> > > Ah, so what you are getting it is that after running a checkout and > some initial steps on a workspace on one machine, you want subsequent > steps on other slaves to use either a lightweight clone of the > workspace (à la ZFS) or a shared mount of it (à la Docker volumes). > This makes sense

Re: Parameterise slaves launched in a cloud [workflow ?]

2014-10-25 Thread Jesse Glick
On Thu, Oct 23, 2014 at 1:41 AM, Nigel Magnay wrote: > Are there any examples of clouds that [honor provisioning requests for the > names of existing slaves]? Not sure. > better parallelism: once the project is built, run the potentially run the 5 > different next steps on different machines

Re: Parameterise slaves launched in a cloud [workflow ?]

2014-10-23 Thread Nigel Magnay
> > > This at least is possible, if your Cloud honors a request for a label > which was actually a previously used Slave.name. There is not much > flexibility here but at least from a Workflow project it might be > feasible. I am not sure what it buys you as opposed to doing all the > build steps w

Re: Parameterise slaves launched in a cloud [workflow ?]

2014-10-22 Thread Jesse Glick
On Wed, Oct 22, 2014 at 4:55 AM, Nigel Magnay wrote: > it may be useful to be able to say "only launch downstream slaves > on the same physical node as the upstream job". This at least is possible, if your Cloud honors a request for a label which was actually a previously used Slave.name. There i

Parameterise slaves launched in a cloud [workflow ?]

2014-10-22 Thread Nigel Magnay
I'm thinking out loud here, but I wonder if it would be nice to be able to support the following scenarios in Jenkins (and docker plugin users have been asking for similar features). I use docker to launch slaves on a variety of boxes. This works very nicely. You can tell docker to attach a 'data