Re: Building with Jenkins slaves
Re: Building with Jenkins slaves
- Subject: Re: Building with Jenkins slaves
- From: Maik Musall <email@hidden>
- Date: Thu, 01 Nov 2012 12:23:01 +0100
Hi Maik, On 01/11/2012, at 9:18 PM, Maik Musall < email@hidden> wrote: I've experimented with that, and the possibilities I found are either
* duplicate jobs and tie each one to specific slaves (not ideal), or
* add a script to upstream builds that distributes the artifacts to all other slaves upon completion.
Thanks for the info. The promising feature of the EC2 plugin is that it will spin up and terminate slaves based on demand. I think both of your possibilities would rely on persistent slave instances, wouldn't they?
They would, I suppose. I'm not familiar with the EC2 plugin and have no EC2 experience anyway. The showstopper for us would already be having source code on external servers that don't belong to us and we don't completely control. The EC2 instances would need to access our internal git server. So I'll stick with internal slaves anyway.
Plus we tend to have rather large build artifacts and frameworks packages, which get distributed to slaves much faster if everything's in the local network.
Maik |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden