On Fri, Jan 14, 2011 at 13:41, Romain Pelisse <bela...@gmail.com> wrote:
> I'm building a staging environement and I would like it to be able to
> redeploy automatically, after each commit - or every hour, some
> applications. Those applications are right now deployed and set up by
> puppet. I wonder if I should use puppet to redeploy those applications after
> each commit, and if I should how trigger, on the puppet, a full
> redeployement of the application ?
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. Puppet can then be set to 'latest' for those packages and
trigger the redeployment based on that change.
That gives a much more robust, repeatable, and automated deployment
solution that ensures you push only if things are work. However, if
you don't care so much you could just use the 'puppetrun' tool to
trigger an agent run on the staging machines, and use whatever
mechanism you prefer to have puppet install the latest version.
Triggering puppetrun should be easy enough to automate based on
whatever post-commit or post-push hooks your VCS supports.
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.
