• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Building with Jenkins slaves
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Building with Jenkins slaves


  • Subject: Re: Building with Jenkins slaves
  • From: Paul Hoadley <email@hidden>
  • Date: Thu, 01 Nov 2012 21:27:12 +1030

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?


-- 
Paul Hoadley
http://logicsquad.net/



 _______________________________________________
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

  • Follow-Ups:
    • Re: Building with Jenkins slaves
      • From: Maik Musall <email@hidden>
References: 
 >Building with Jenkins slaves (From: Paul Hoadley <email@hidden>)
 >Re: Building with Jenkins slaves (From: Maik Musall <email@hidden>)

  • Prev by Date: Re: Building with Jenkins slaves
  • Next by Date: Re: Building with Jenkins slaves
  • Previous by thread: Re: Building with Jenkins slaves
  • Next by thread: Re: Building with Jenkins slaves
  • Index(es):
    • Date
    • Thread