These slaves are on-demand. If they aren't setup properly to begin with, a lot of the value is lost.
If it takes us 30 minutes for an on-demand slave to be ready to do any work, especially if it was to run a 3 minute job, there was no point in the first place. That said, most of the work done for the Ansible stuff was translated into a combination of packer and puppet for building the image itself. See tools/packer in Infra's SVN tree. --David On Fri, Aug 22, 2014 at 7:14 PM, Giridharan Kesavan <[email protected]> wrote: > Hi Andrew, > > We could use the ansible playbook to setup these slaves as well, it takes > care of setting up the right svn version and settings.xml and other > things.. > > -giri > > > On Fri, Aug 22, 2014 at 2:52 PM, Andrew Bayer <[email protected]> > wrote: > >> FYI, we discovered a couple things missing (~jenkins/.m2/settings.xml >> and SVN 1.6 most notably), so I'm taking the slaves offline until we >> have a new image. >> >> A. >> >> On Fri, Aug 22, 2014 at 1:58 PM, Andrew Bayer <[email protected]> >> wrote: >> > FYI - we've enabled burst capacity on-demand Ubuntu slaves run on >> > Rackspace for builds.apache.org - they're on the ubuntu label. The >> > image should be good, but if you see any strange issues where builds >> > pass on the existing ubuntu-* boxes but not on >> > jenkins-ubuntu-1404-4gb-*, please let us know by opening a BUILDS >> > JIRA. Thanks! >> > >> > A. >> > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You.
