Skip to content

Commit 590992e

Browse files
authored
Update applications-dashboard.md (#313)
* Update applications-dashboard.md Added manual rollback for rollout * Update applications-dashboard.md
1 parent 7eb3668 commit 590992e

File tree

1 file changed

+37
-0
lines changed

1 file changed

+37
-0
lines changed

_docs/deployment/applications-dashboard.md

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -583,6 +583,9 @@ You can:
583583
* [Monitor CI details by deployments](#monitor-ci-details-by-deployment)
584584
* [Monitor updated resources by deployment](#monitor-updated-resources-by-deployment)
585585
* [Monitor rollouts by deployment](#monitor-rollouts-by-deployment)
586+
* [Manually rollback completed rollout to previous revision](#manually-rollback-completed-rollout-to-previous-revision)
587+
588+
586589

587590

588591
**How to monitor deployments**
@@ -718,7 +721,41 @@ The table lists the controls in the Rollout Player to manage an ongoing rollout.
718721
| **Skip step** {::nomarkdown}<img src="../../../images/icons/rollout-skip-step.png" display=inline-block"> {:/} | Skip execution of current step. Such steps are marked as Skipped in the rollout visualization. |
719722
| **Promote full rollout** {::nomarkdown}<img src="../../../images/icons/rollout-promote-full.png" display=inline-block"> {:/} | Skip remaining pause, traffic routing, and analysis steps, and deploy the current release. |
720723

724+
#### Manually rollback completed rollout to previous revision
725+
<!--- add screenshots -->
726+
Manually rollback a completed rollout to a previous revision when and if needed. If after a successful analysis run and rollout, your application is not functioning as it should, you can rollback to a prior revision from the Rollout’s revision history. The revision depth is determined by the `spec.revisionHistoryLimit` parameter in the [Rollout Specification](https://argoproj.github.io/argo-rollouts/features/specification/#rollout-specification){:target="\_blank"}.
727+
Manual rollback changes the live state of the rollout resource to the state in the previous commit that you select.
728+
729+
1. In the Codefresh UI, select [Applications](https://g.codefresh.io/2.0/applications-dashboard/list){:target="\_blank"}.
730+
1. Select the application and select the **Timeline** tab.
731+
1. Click the name of the rollout to rollback.
732+
733+
{% include
734+
image.html
735+
lightbox="true"
736+
file="/images/whats-new/rel-notes-jan23-rollout-rollback.png"
737+
url="/images/whats-new/rel-notes-jan23-rollout-rollback.png"
738+
alt="Completed Rollout in Timeline"
739+
caption="Completed Rollout in Timeline"
740+
max-width="60%"
741+
%}
742+
743+
{:start="4"}
744+
1. From the **Choose version to Rollback** dropdown, select the revision to rollback to.
745+
746+
{% include
747+
image.html
748+
lightbox="true"
749+
file="/images/whats-new/rel-notes-jan23-rollout-rev-select.png"
750+
url="/images/whats-new/rel-notes-jan23-rollout-rev-select.png"
751+
alt="Select rollout revision for rollback"
752+
caption="Select rollout revision for rollback"
753+
max-width="60%"
754+
%}
721755

756+
{:start="5"}
757+
1. Review the changes in the revision.
758+
1. In the Rollout Player, click **Rollback to**.
722759

723760
##### View analysis run
724761
If you have defined an analysis template for the rollout, you can check the run results and the manifest.

0 commit comments

Comments
 (0)