Canceling the deployment doesn't create a new revision, but keeps the app's instances on the previous revision (3). I believe what's happening here is the first rollback creates a new revision (4). Revision description deployable revision guid created atĤ New droplet deployed. Getting revisions for app app_name in org org / space space as admin. This command is in EXPERIMENTAL stage and may change without notice The rollback fails with the following error:
SMARTSVN ROLLBACK TO REVISION LOCALLY CODE
However, it's responding as if it believes the rollback was completed successfully and that I'm trying to rollback from revision #4 which does have the same code and configs as revision cloudfoundry/capi-release#1 Current result I'd expect the rollback to succeed without error since the previous rollback to revision 1 was cancelled and the currently deployed revision is revision 3 - which doesn't share the same droplet as revision 1.Ī new revision cloudfoundry/capi-release#4 was created during the cancelled rollback, but the system still appears to think the currently deployed revision is revision cloudfoundry/capi-release#3Ĭf curl /v3/apps/$(cf app app_name -guid)/revisions/deployed
![smartsvn rollback to revision locally smartsvn rollback to revision locally](https://i.imgur.com/0Fwlp1z.png)
open two terminals and target the same env/org/space.Using the latest edge version of the v7 CLI