# Application rollback with ansible

**URL:** <https://forum.ansible.com/t/application-rollback-with-ansible/18312>\
**Category:** Ansible Project\
**Created:** [May 26, 2015, 4:58pm UTC](https://forum.ansible.com/t/application-rollback-with-ansible/18312 "2015-05-26T16:58:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jack\_P](https://avatars.discourse-cdn.com/v4/letter/j/0ea827/32.png) [@Jack\_P](https://forum.ansible.com/u/Jack_P)\
**Post date:** [May 26, 2015, 4:58pm UTC](https://forum.ansible.com/t/application-rollback-with-ansible/18312/1 "2015-05-26T16:58:00Z")

</div>

Hi!

I was hoping to canvas opinion on how people using ansible handle rollbacks. We’re migrating a large multihost multi-app project and have have two competing opinions:

1. Utilise idempotency and simply redeploy a previous working set on a failure (which should only deploy the systems which have changed versions)
2. Maintain historical versions of applications on hosts and use symlinks to rollback.

What is your experience or preference?

Thanks,

Jack

---

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [May 26, 2015, 11:09pm UTC](https://forum.ansible.com/t/application-rollback-with-ansible/18312/2 "2015-05-26T23:09:19Z")

</div>

Look to the new v2 engine which has 'exception handling' built into task blocks.

---

<div class="post-metadata">

**Author:** ![Jeff\_Reter](https://avatars.discourse-cdn.com/v4/letter/j/a88e4f/32.png) [@Jeff\_Reter](https://forum.ansible.com/u/Jeff_Reter)\
**Post date:** [May 27, 2015, 7:03am UTC](https://forum.ansible.com/t/application-rollback-with-ansible/18312/3 "2015-05-27T07:03:04Z")

</div>

when will v2 be stable?