You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Rollback an applicationtoa previous deployment version.
19
19
20
20
21
21
*[Manage rollouts for deployments](#manage-rollouts-for-deployments)
22
22
Control ongoing rollouts by resuming indefinitely paused steps, promoting rollouts, aborting, restarting and retrying rollouts.
23
23
24
+
*[Delete applications](#delete-an-application)
25
+
Delete unused or legacy applications to avoid clutter and remove unnecessary resources.
26
+
24
27
25
28
26
29
@@ -219,41 +222,99 @@ For example, if you made changes to `api` resources or `audit` resources, type `
219
222
<br><br>
220
223
{:/}
221
224
222
-
##Delete an application
223
-
Delete an application from Codefresh. Deleting an application deletes the manifest from the Git repository, and then from the cluster where it is deployed. When deleted from the cluster, the application is removed from the GitOps Apps dashboard in Codefresh.
225
+
##Rollback GitOps applications
226
+
Rollback to a previously deployed version of active GitOps applications. You may want to rollback a newly deployed version due to errors in your code or misconfigurations, etc.
227
+
228
+
###Prerequisites for rollback
229
+
230
+
Rollback can be disabled for the following reasons:
231
+
232
+
***Auto-sync ON for applications**
233
+
If auto-sync is`ON`, the default behavior for GitOps is to sync the cluster with the desired state in Git. The Rollback button is disabled with a tooltip.
234
+
235
+
236
+
For application rollback, auto-sync must be`OFF`. The quickest and easiest way to identify auto-sync status is through the Application Header.
237
+
To change the setting,[edit]({{site.baseurl}}/docs/deployments/gitops/manage-application/#edit-application-definitions) the application's[General configuration settings]({{site.baseurl}}/docs/deployments/gitops/create-application/#application-general-configuration-settings).
***Deployment version for rollback older than history limit**
251
+
By default, you can rollback to any the previous ten deployments (same as Argo CD).
252
+
If you try to rollback 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'.
253
+
254
+
>TIP:
255
+
>To configure a different number, edit the application manifest and add`RevisionHistoryLimit` set to the number of previous deployments you need in the`spec` section.
224
256
225
-
>**Prune resources** in the application's General settings determines the scope of the delete action.
226
-
When selected, both the application and its resources are deleted. When cleared, only the application is deleted. For more information, review[Sync settings]({{site.baseurl}}/docs/deployments/gitops/create-application/#sync-settings).
227
-
Codefresh warns you of the implication of deleting the selected application in the Delete form.
228
257
229
-
1. In the Codefresh UI, from Ops in the sidebar, select[GitOps Apps](https://g.codefresh.io/2.0/applications-dashboard/list){:target="\_blank"}.
230
-
1. Select theapplicationto delete.
231
-
1. Click the three dots for additional actions, and select**Delete**.
258
+
***Deleted version of application**
259
+
You can activate rollback only for_new_ and currently activeapplicationversions that are deployed.
260
+
If you deleted an application and then recreated it with the same name, you cannot rollback to the deleted version or to any version prior to the deletion. The Rollback button is disabled with a tooltip.
Control ongoing rollouts by resuming indefinitely paused steps, promoting rollouts, aborting, restarting and retrying rollouts.
@@ -365,6 +426,44 @@ The table describes the options for the `Rollout` resource.
365
426
|**Retry**| Retry a rollout that has been aborted. Available only when a rollout has been aborted.|
366
427
|**Skip-current-step**| Skip executing the current step, and continue with the next step.|
367
428
429
+
##Delete an application
430
+
Delete an application from Codefresh. Deleting an application deletes the manifest from the Git repository, and then from the cluster where it is deployed. When deleted from the cluster, the application is removed from the GitOps Apps dashboard in Codefresh.
431
+
432
+
>**Prune resources** in the application's General settings determines the scope of the delete action.
433
+
When selected, both the application and its resources are deleted. When cleared, only the application is deleted. For more information, review[Sync settings]({{site.baseurl}}/docs/deployments/gitops/create-application/#sync-settings).
434
+
Codefresh warns you of the implication of deleting the selected application in the Delete form.
435
+
436
+
1. In the Codefresh UI, from Ops in the sidebar, select[GitOps Apps](https://g.codefresh.io/2.0/applications-dashboard/list){:target="\_blank"}.
437
+
1. Select the application to delete.
438
+
1. Click the three dots for additional actions, and select**Delete**.
439
+
440
+
{% include
441
+
image.html
442
+
lightbox="true"
443
+
file="/images/applications/app-delete-option.png"
444
+
url="/images/applications/app-delete-option.png"
445
+
alt="Delete application"
446
+
caption="Delete application"
447
+
max-width="80%"
448
+
%}
449
+
450
+
Pay attention to the_impact of the delete action_ for the selected application that Codefresh displays.
Copy file name to clipboardExpand all lines: _docs/whats-new/release-notes.md
+14-13Lines changed: 14 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,13 +5,14 @@ group: whats-new
5
5
toc:true
6
6
---
7
7
8
-
Welcome to our unified Release Notes, including Codefresh pipelines and Codefresh GitOps!
8
+
Welcome to our unified Release Notes, including Codefresh pipelines and Codefresh GitOps! If you missed online announcements, this is where you can find the new features, enhancements, and bug fixes.
9
+
9
10
10
11
##March 2023
11
12
12
13
###Features & Enhancements
13
14
14
-
####CI/CD: Selective restart for failed build steps
15
+
####Pipelines: Selective restart for failed build steps
15
16
We added the**Restart from a failed step** as an option to the pipeline's Policy settings, which you can enable/disable per pipeline.
16
17
{% include
17
18
image.html
@@ -34,7 +35,7 @@ For details, see [Policy settings for pipelines]({{site.baseurl}}/docs/pipelines
34
35
35
36
<br>
36
37
37
-
####CI/CD: Datadog integration enhancements
38
+
####Pipelines: Datadog integration enhancements
38
39
We enhanced our integration with Datadog to report additional information from Codefresh pipelines in Datadog.
39
40
<br>
40
41
The new information should make it even easier to monitor and analyze Codefresh pipelines in Datadog:
@@ -60,7 +61,7 @@ See [Datadog pipeline integration]({{site.baseurl}}/docs/integrations/datadog/).
60
61
61
62
62
63
63
-
####CI/CD: Override runtime environment for GitOps pipeline integrations
64
+
####Pipelines: Override runtime environment for GitOps pipeline integrations
64
65
A GitOps pipeline integration uses the default runtime environment. After creating a GitOps pipeline integration, you can now override its runtime environment.
65
66
Codefresh uses the runtime environment for system actions such as Rollback.
66
67
@@ -135,7 +136,7 @@ See [Monitoring GitOps applications]({{site.baseurl}}/docs/deployments/gitops/ap
135
136
136
137
###Bug fixes
137
138
138
-
####CI/CD
139
+
####Pipelines
139
140
* Triggers for inactive webhooks return 200.
140
141
* In full-screen view mode, the pipeline list panel on the left overlaps the pipeline YAML.
141
142
* Unable to override image used for`cf-runtime-lv-monitor Daemonset` in the Runner Helm chart.
@@ -169,7 +170,7 @@ See [Monitoring GitOps applications]({{site.baseurl}}/docs/deployments/gitops/ap
169
170
170
171
###Features & Enhancements
171
172
172
-
####CI/CD: Slack integration notification for builds terminated by system
173
+
####Pipelines: Slack integration notification for builds terminated by system
173
174
Notifications for failed builds are equally, if not more important, than those for successful builds. Getting notifications for system-terminated builds is crucial, as it indicates that the build was stopped because of pipeline policy and may require immediate attention. You can quickly investigate the issue and take corrective action if necessary.
174
175
175
176
@@ -199,15 +200,15 @@ Here's an example of the notification you would receive in Slack.
199
200
200
201
<br>
201
202
202
-
####CI/CD: Multiple Helm contexts for pipelines
203
+
####Pipelines: Multiple Helm contexts for pipelines
203
204
With support for multiple Helm registry contexts in the same pipeline, dependencies in any of the imported Helm registry contexts in the Helm chart are automatically authenticated and added.
204
205
For the Helm`install` and`push` actions, you can select the primary Helm registry context for the command.
205
206
For details, see[Import Helm configurations into your pipeline definition]({{site.baseurl}}/docs/deployments/helm/using-helm-in-codefresh-pipeline/#step-4-optional-import-helm-configurations-into-your-pipeline-definition) and[Action modes]({{site.baseurl}}/docs/deployments/helm/using-helm-in-codefresh-pipeline/#helm-step-action-modes).
206
207
207
208
208
209
<br>
209
210
210
-
####CI/CD: Multiple cache sources for pipeline builds
211
+
####Pipelines: Multiple cache sources for pipeline builds
211
212
212
213
Docker has support for specifying external cache sources for builds. We added the`cache-from` argument to our`build` step allowing you to specify additional cache sources and speed up the build process. Multiple cache sources are useful when your primary cache source is unavailable or slow.
213
214
@@ -236,7 +237,7 @@ For details, see [`cache_from` in `build` step fields]({{site.baseurl}}/docs/pip
236
237
237
238
<br>
238
239
239
-
####CI/CD: Control thresholds for memory usage warning banner
240
+
####Pipelines: Control thresholds for memory usage warning banner
240
241
Remember the banner that alerted you whenever the memory usage for a pipeline build exceeded 70 or 90%?
241
242
You can now decide the usage threshold at which to display the banner. Increasing the threshold helps avoid premature warnings for pipelines that do not consume a lot of memory, while decreasing it for resource-intensive pipelines helps avoid build failures.
242
243
@@ -259,7 +260,7 @@ See [Memory usage warning for pipeline builds]({{site.baseurl}}/docs/pipelines/c
259
260
260
261
<br>
261
262
262
-
####CI/CD: New flow for Cloud Builds for pipelines
263
+
####Pipelines: New flow for Cloud Builds for pipelines
263
264
Previously, all Codefresh accounts had access to a SaaS runtime environment to run pipelines. However, this is no longer the case. Account administrators can request SaaS runtime environments by clicking**Enable Cloud Builds** in Codefresh. This action triggers an email request to Codefresh, and you should receive a response within 24 hours.
264
265
265
266
@@ -275,7 +276,7 @@ For details, see [Argo CD Releases](https://github.com/argoproj/argo-cd/releases
275
276
####Usability enhancements
276
277
Saves time and ease of use in interactions with Codefresh.
277
278
278
-
***CI/CD: Prompt to switch accounts**
279
+
***Pipelines: Prompt to switch accounts**
279
280
To avoid confusion, when you are signed into more than one Codefresh account, you are prompted to either switch to the active account or return to the previous one.
280
281
281
282
{% include
@@ -288,7 +289,7 @@ Saves time and ease of use in interactions with Codefresh.
288
289
max-width="50%"
289
290
%}
290
291
291
-
***CI/CD: Case-insensitive search for Pipelines and Pipeline List view**
292
+
***Pipelines: Case-insensitive search for Pipelines and Pipeline List view**
292
293
Search is now easier as queries are case-insensitive.
293
294
294
295
***GitOps: Terminate Sync now in application header**
@@ -313,7 +314,7 @@ See [Application header]({{site.baseurl}}/docs/deployments/gitops/applications-d