Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Add new rollback player buttons#989

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
NimRegev merged 2 commits intomasterfromgitops-rollout-player-buttons
May 28, 2024
Merged
Show file tree
Hide file tree
Changes fromall commits
Commits
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions_docs/deployments/gitops/applications-dashboard.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -771,8 +771,8 @@ The table lists the controls in the Rollout Player to manage an ongoing rollout.


#### View analysis run
If you have defined ananalysis template for the rollout, you can check the run results and the manifest.
The result of ananalysis run determines if the rollout is completed, paused, or aborted. For detailed information, see the [Analysis section in Argo Rollouts](https://argoproj.github.io/argo-rollouts/features/analysis/){:target="\_blank"}.
If you have defined anAnalysisTemplate for the rollout, you can check the run results and the manifest.
The result of anAnalysisRun determines if the rollout is completed, paused, or aborted. For detailed information, see the [Analysis section in Argo Rollouts](https://argoproj.github.io/argo-rollouts/features/analysis/){:target="\_blank"}.

If you are running Background Analysis for example, the first step shows the list of analysis metrics.

Expand Down
14 changes: 8 additions & 6 deletions_docs/deployments/gitops/manage-application.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -368,7 +368,7 @@ As an alternative to manually syncing an application, either refresh or hard ref
%}

## Rollback Argo CD applications
Rollback to a previously deployed version of active Argo CD applications. You may want torollback a newly deployed version due to errors in your code or misconfigurations, etc.
Rollback to a previously deployed version of active Argo CD applications. You may want toroll back a newly deployed version due to errors in your code or misconfigurations, etc.

### Prerequisites for rollback

Expand All@@ -393,8 +393,8 @@ max-width="80%"
%}

* **Deployment version for rollback older than history limit**
By default, you canrollback to any the previous ten deployments (same as Argo CD).
If you try torollback to a deployment older than ten of the most recent deployments, the Rollback option is disabled with a tooltip, that the 'Release is not in history'.
By default, you canroll back to any the previous ten deployments (same as Argo CD).
If you try toroll back to a deployment older than ten of the most recent deployments, the Rollback option is disabled with a tooltip, that the 'Release is not in history'.

{{site.data.callout.callout_tip}}
**TIP**
Expand DownExpand Up@@ -515,9 +515,11 @@ The table describes the controls in the Rollout Player.
{: .table .table-bordered .table-hover}
| Rollback player option | Description |
| -------------- | ------------|
| **Rollback** | Not available currently. |
| **Rollback** | Rolls back to the previous deployment. See also [Prerequisites for rollback](#prerequisites-for-rollback). |
|**Abort** | Terminate the current rollout. |
| **Pause** | Pause the rollout. If the rollout is already automatically paused as the result of a step definition, clicking Pause pauses the rollout also after the pause duration. |
| **Resume** <!---{::nomarkdown}<img src="../../../images/icons/rollout-resume.png" display=inline-block"> {:/}-->| Resume a rollout that was paused either manually by clicking Pause, or automatically through the step's definition. |
|**Retry** | Retry a rollout that has been aborted. Restarts the rollout from the beginning. Available only when a rollout has been aborted. |
| **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. |
| **Promote full** <!---{::nomarkdown}<img src="../../../images/icons/rollout-promote-full.png" display=inline-block"> {:/} --> | Skip all remaining steps, and deploy the current image. |

Expand All@@ -536,9 +538,9 @@ Manual rollback changes the live state of the rollout resource to the state in t
1. In the Rollout Player, click **Rollback to**.


### Manage the`rollout` resource
### Manage theRollout resource

Control the rollout through the options available for the Rollout resource.
Control the rollout through the options available for the Rollout resource in the Current State tab.

1. In the Codefresh UI, from Ops in the sidebar, select [GitOps Apps](https://g.codefresh.io/2.0/applications-dashboard/list){:target="\_blank"}.
1. Select the application and go to the Current State tab.
Expand Down
[8]ページ先頭
©2009-2025 Movatter.jp