example42/puppi

Feature: continuous deploy

k9ert opened this issue · 2 comments

I was not aware, that the the auto_deploy feature will only be triggered once. To make something like continuos deployment possible, puppi probably needs a new flag for that, e.g. cont_deploy => true

Would you be happy and integrate it if i would do it or do you have general concerns about such a feature?

Obviously, you need a strong and early check, whether the deployment needs to be done ...

To be honest I don't think Puppet is the right tool to manage application deployments or run puppi deploys.
The auto_deploy makes sense if you want to have a new, complete, server provisioned from scratch.
For continuos deployments I followed different approaches, according to situations:

  • Run puppi deploy via cron (check also the option always_deploy , by default is yes, but it you set to no a deploy is done olny when the source checksum changes, so that do you risk to re-deploy something which is already there)
  • Run puppi via jenkins (using the ssh plugin and sudo)
  • Run puppi via mcollective.

What do you think, do these alternatives fit your case?

The jenkins-ssh-plugin is probably what's works best for me. Thanks for the clearification.