# what is the standard Ansible rolling-deploy with continuous integration testing workflow?

**URL:** <https://forum.ansible.com/t/what-is-the-standard-ansible-rolling-deploy-with-continuous-integration-testing-workflow/15422>\
**Category:** Ansible Project\
**Tags:** aws\
**Created:** [June 6, 2014, 11:48pm UTC](https://forum.ansible.com/t/what-is-the-standard-ansible-rolling-deploy-with-continuous-integration-testing-workflow/15422 "2014-06-06T23:48:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gallagher\_Polyn](https://avatars.discourse-cdn.com/v4/letter/g/94ad74/32.png) [@Gallagher\_Polyn](https://forum.ansible.com/u/Gallagher_Polyn)\
**Post date:** [June 6, 2014, 11:48pm UTC](https://forum.ansible.com/t/what-is-the-standard-ansible-rolling-deploy-with-continuous-integration-testing-workflow/15422/1 "2014-06-06T23:48:45Z")

</div>

Hey all,

Happily (and with help from folks on this forum) I am able to do rolling deploys a la the lamp\_haproxy [example](https://github.com/ansible/ansible-examples/tree/master/lamp_haproxy) on all of the providers covered by Ansible’s cloud modules: rackspace, aws, do, linode and gce – yay!

Next up: how would [github.com/ansible/ansible-examples/tree/master/lamp\_haproxy](http://github.com/ansible/ansible-examples/tree/master/lamp_haproxy) be modified or used in context with a CI component?

I can’t now find the few Ansible configuration references I may have seen shown in online presentations by Michael or Tim, but I think I recall they each showed a CI step directly in the context of a rolling deploy playbook? Is that right? If not, I might expect the flow to be something like: git pull, CI server tests pass, CI server kicks off rolling deploy.

Any references to latest-greatest web app CI-Ansible strategies greatly appreciated. Here are the two that most interest me:

- [developer.rackspace.com/blog/move-fast-and-dont-break-things-testing-with-jenkins-ansible-and-docker.html](http://developer.rackspace.com/blog/move-fast-and-dont-break-things-testing-with-jenkins-ansible-and-docker.html)

- [www.activestate.com/blog/2014/01/using-docker-run-ruby-rspec-ci-jenkins](http://www.activestate.com/blog/2014/01/using-docker-run-ruby-rspec-ci-jenkins)

Thanks,

G

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [June 8, 2014, 3:34pm UTC](https://forum.ansible.com/t/what-is-the-standard-ansible-rolling-deploy-with-continuous-integration-testing-workflow/15422/2 "2014-06-08T15:34:56Z")

</div>

Usually you would have something like:

Jenkins build  
if successful, call rolling update in stage  
if successful, call rolling update in prod