Why not use Ansible directly? Your five tasks would map directly to tasks within a playbook:
1. Create a directory using the file module <http://docs.ansible.com/ansible/file_module.html> 2. To support rollback, you could move any currently-deployed jar files to a known rollback location on the host(s) 3. Copy a local jar to the host(s) using the copy module <http://docs.ansible.com/ansible/copy_module.html> 4. Upload a templatized e.g. systemd service for your Dropwizard application 5. Restart it using the service module <http://docs.ansible.com/ansible/service_module.html> On Thu, Jul 21, 2016 at 4:27 PM, S Ahmed <[email protected]> wrote: > Hello! > > Is there any deployment type project that uses e.g. Ansible that deploys a > dropwizard project to production by: > > 1. creating a new folder > 2. waits till the files have been uploaded > 3. stops the current deployed version > 4. starts the new deployed version > > Does this exist at the moment? > > 5. Ability to rollback would be a bonus :) > > > Thanks! > > -- > You received this message because you are subscribed to the Google Groups > "dropwizard-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Evan Meagher -- You received this message because you are subscribed to the Google Groups "dropwizard-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
