On Fri, Jan 14, 2011 at 14:26, Romain Pelisse <bela...@gmail.com> wrote:
>> Personally, I would use some sort of CI solution like Hudson that
>> would be triggered on commit. As part of the configured project you
>> could have a full test suite run and if (and only if) it was entirely
>> successful build new OS packages and push that artefact up to your
>> repository.
>
> That's exactly what we are doing (I should have perhaps be more clear)
*nod*
>> Puppet can then be set to 'latest' for those packages and
>> trigger the redeployment based on that change.
>
> This is exactly what I want to do, however those application are not package
> as rpm or deb but simply zipfile. Indeed, the applications are Java based
> application runned by daemontools. We simply unzip them and let daemontools
> start them.
...so you need to take manual action to have puppet notice that the
version has changed. One of the advantages of using something like an
RPM is that someone else already wrote all the infrastructure to make
that happen and all. :)
OTOH, if you just drop that zip into place where a puppet file server
can see it, and use a 'file' resource with a source of
'puppet://ci-server.local/application.zip', then 'notify' to an exec
that unpacks and installs the zip file you can get the right thing
done...
> "In lieu of" Yum or Apt, we use Ivy. But even if we were to use Yum/Apt, and
> set upgradeable to the appropriate package, I don't think (or I didn't
> understand something) that it would trigger the puppet to upgrade
> automatically, as soon as the package is made available by the CI tool (in
> our case Hudson).
> ... or I miss something ?
Sorry, I was assuming that you already have puppet running routinely
on the staging machines. If you need something faster than your
normal checkin interval...
> At first glance, sounds that puppetrun is probably a better option. I have
> to look into it (never really used it).
...then puppetrun or mcollective would be the right tool for the job.
(...or any other tool to run puppet agent on those machines, of
course. :)
My assumptions were showing there, too, where I didn't make what I was
envisioning clear enough.
Regards,
Daniel
--
✉ Daniel Pittman <dan...@rimspace.net>
⌨ dan...@rimspace.net (XMPP)
☎ +1 503 893 2285
♻ made with 100 percent post-consumer electrons
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
