On Jan 14, 1:41 pm, Romain Pelisse <bela...@gmail.com> wrote: > Hi, > > 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 ? >
It depends on how you deploy your applications. In the case of packaged applications I do the following after tests pass in Hudson: 1) using extconf to specify versions and overwrite the package version of the file with a script 2) use mcollective to go out and run apt-get update and install a specific version 3) use mcollective to audit the package versions and send a report I use the extconf file because I do the same for production and want to pin versions. You could just set your stage to latest and run an mcollective client to just kick off your install. -c -- 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.
