← Back to team overview

canonical-ci-engineering team mailing list archive

Re: Autorestarting jenkins slaves

 

>>>>> Evan Dandrea <evan.dandrea@xxxxxxxxxxxxx> writes:

<snip/>

    >> Since we don't want the former, the later requires creating 40 copies (I
    >> kind of understand why it's done this way for phones, but 40 ??? /me
    >> faint).

    > Couldn't we do this programmatically? Alternatively, couldn't we have
    > a job that uses the instance field:

    > http://upstart.ubuntu.com/cookbook/#instance

Yup, that seems to fit perfectly, thanks !

I'll dig it asap... or not given my current schedule :-/

<snip/>

    >> None of that is lightweight so far which is why I stopped and thought
    >> about ssh which at least put the burden on the server itself (bar the
    >> ssh key deployment but that should be a once only thing). But then Larry
    >> rightly raised the previous issue with that.

    > A package would work as well. 

Yeah and if all hosts requiring that package were registered with
landscape, the deploy story may not be that bad.

That would leave us with a single configuration file to maintain on each
host listing the slaves nodes.

    > I merely picked /srv because that's what IS uses. They're at least
    > using Puppet (old services) or Juju (new services). The format is
    > roughly:

Ack. Ok, clearer. Yeah, I've thought about that but found it a bit to
dirty to spend time on it rather than charming (and the balance is quite
tight if we have to restart such slaves only once or twice a week).

      Vincent


References