Great news fellow developers, OpenShift now supports deployment history complete with the ability to rollback to a previous version of your application. Why is this important? I will be the first to admit to having pushed things to production only to find a new bug that is critical in nature and has to be fixed immediately. The most obvious way to handle this is to rollback the application code to the last known working state while developers can work to resolve the defect in the software. Throughout my years in development and managing system administrators, I have seen various methods to solve this problem including versioning RPMS and keeping them in a repository to backing up the gold build of the .war or .ear file in Javaland. During this blog post, I will introduce you to deployment and rollback strategy we have implement for all users of the OpenShift PaaS.