<p>The answer, no.</p>

<p>The best ways to rollback would be to use <code>git revert</code>, which then adds the rollback to history (which is a good thing), and then push that like any other commit. The other would be to use the git hash of the commit you'd like to rollback to and build it with the CircleCI API.</p>

<p>Right now, you could also attempt to rebuild and older build via the UI but this isn't suggest for deploys &amp; Workflows. Too many variables for safe, reproducible deploys.</p>

<p>- Ricardo N Feliciano<br>
Developer Evangelist, CircleCI</p>

CC BY-SA 4.0
2021-07-31T15:10:11.943Z
The problem with this is that you need to rebuild containers.  Rolling back to a previous container, without rebuilding it, reduces the risk of introducing new bugs.  New container means new test cycle, which means delaying a potentially critical rollback.
Joe Cairns
CC BY-SA 3.0
2017-07-10T17:00:39.657Z
2017-07-10T17:00:39.657Z
FelicianoTech
<p>The new CircleCI 2.0 configuration allows to have a step of type <code>approve</code> which waits for user input. Is there some way to not just deploy code using manual stop, but also have a rollback to a previous version based on user input?</p>

CC BY-SA 3.0
2017-07-10T16:19:51.597Z
Like git revert?
FelicianoTech
CC BY-SA 3.0
2017-07-10T16:59:40.613Z
The scenario I was thinking is deployment of the previous build artifact back. It seems there is only a deployment of current artifact, no way to specify which.
Evgeny Zislis
<circleci-2.0>
CircleCI manually approved Deployment with Rollback
Evgeny Zislis
# CircleCI manually approved Deployment with Rollback

(Asked by: username_0 on 2017-07-09)

The new CircleCI 2.0 configuration allows to have a step of type `approve` which waits for user input. Is there some way to not just deploy code using manual stop, but also have a rollback to a previous version based on user input?

**Tags:** circleci-2.0

> **Comments:**
> **username_1**: Like git revert?  
> **username_0**: The scenario I was thinking is deployment of the previous build artifact back. It seems there is only a deployment of current artifact, no way to specify which.  

---

## 1 answers

### Answer by username_1 on 2017-07-10. Score: 1

The answer, no.

The best ways to rollback would be to use `git revert`, which then adds the rollback to history (which is a good thing), and then push that like any other commit. The other would be to use the git hash of the commit you'd like to rollback to and build it with the CircleCI API.

Right now, you could also attempt to rebuild and older build via the UI but this isn't suggest for deploys & Workflows. Too many variables for safe, reproducible deploys.

- Ricardo N Feliciano  
Developer Evangelist, CircleCI

> **Comments:**
> **username_2**: The problem with this is that you need to rebuild containers.  Rolling back to a previous container, without rebuilding it, reduces the risk of introducing new bugs.  New container means new test cycle, which means delaying a potentially critical rollback.  

---

