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
Promotion Workflows (Argo Workflows) automate environment-specific tests and validations before and after promotion.
46
-
* Create and use Promotion Workflows to run smoke tests, database validation, and other requirements to verify readiness.
48
+
* Create Promotion Workflows to run smoke tests, database validation, and any other requirements to verify readiness of each application in an environment.
49
+
50
+
1.[Create Promotion Workflows with hooks]({{site.baseurl}}/docs/promotions/promotion-hooks/)
51
+
Promotion hooks provide promotion status and custom information for releases and environments during the Promotion Flow.
52
+
* Create hooks in Promotion Workflows to implement actions such as Slack notifications
53
+
* Define and export promotion contexts in hooks to expose and pass custom parameters such as Jira ID
Copy file name to clipboardExpand all lines: _docs/promotions/product-releases.md
+9-9Lines changed: 9 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -7,12 +7,11 @@ toc: true
7
7
8
8
9
9
10
-
10
+
## Releases for promotions in GitOps
11
11
Releases in Codefresh GitOps offer a consolidated view of the deployment lifecycle for a product as it progresses through environments during a promotion. They enable you to track, visualize, and analyze changes from the initial trigger to the final deployment, providing comprehensive insights for all stakeholders.
12
12
13
13
A release is automatically created whenever a promotion is triggered for a product, either manually or through an automated flow. This ensures every change is documented and linked to its promotion lifecycle, giving teams complete visibility into their deployment processes.
14
14
15
-
## Releases in GitOps
16
15
In the context of GitOps, a release captures the progression of a product as it is promoted through environments. The release reflects the collective state of all environments and workflows involved in deploying a change, from the initial trigger to the final target environment, whether production or another specified target.
17
16
18
17
@@ -28,7 +27,7 @@ max-width="60%"
28
27
%}
29
28
30
29
### Why Releases matter
31
-
Whether you are a product manager or an application developer, Releases offer:
30
+
Whether you are a product manager or an application developer, releases offer:
32
31
* Lifecycle visualization: Clearly track the deployment lifecycle of a product
33
32
* Integrated change list: Access a unified list of changes leading to a deployment
34
33
* Deployment status: Monitor ongoing deployments and quickly identify issues
@@ -64,7 +63,7 @@ There are two key aspects of tracking deployments for a product through releases
64
63
65
64
##### Release promotion flow
66
65
Track the release visually to monitor its progression through each phase of the promotion lifecycle across environments.
67
-
Specific Release views centralizes all information, allowing you to:
66
+
Release views centralizes all information, allowing you to:
68
67
* Identify and resolve deployment issues without switching between tools
69
68
* Access everything you need to troubleshoot errors in one place.
70
69
@@ -82,7 +81,7 @@ Release notes compile changes from various sources into a single view, enabling
82
81
See [Analyze change history in Release Notes](#analyze-change-history-in-release-notes).
83
82
84
83
85
-
## View Releases for products
84
+
## View releases for products
86
85
87
86
The Releases tab for a product displays the releases for that product, whether successful or failed.
88
87
@@ -145,7 +144,7 @@ max-width="60%"
145
144
The header in the Releases page summarizes the change that triggered the promotion, the overall status of the release, and the count of failed, successful, running, and pending environments.
146
145
147
146
>**NOTE:**
148
-
The commit details are always for the trigger environment that initiated the promotion.
147
+
The commit details are always for the Trigger Environment that initiated the promotion.
149
148
150
149
{% include
151
150
image.html
@@ -186,8 +185,8 @@ max-width="60%"
186
185
187
186
## Environments in product releases
188
187
189
-
The graphical view of the different environments defined in the Promotion Flo allows you to:
190
-
* Understand the interconnections between the environments, whether sequential or parallel.
188
+
The graphical view of the different environments defined in the Promotion Flow allows you to:
189
+
* Understand the interconnections between the environments, whether sequential or parallel
191
190
* Visualize the dependencies between environments to see how changes propagate through the deployment process
192
191
193
192
Each environment is color-coded to indicate the overall status of the promotion for that environment.
@@ -253,8 +252,9 @@ If there is an update that triggers a Pre- or Post-Action Workflow within an env
253
252
For example, if an update in the `staging` environment triggers the `echo-pre-action` Pre-Action Workflow, and a later update in the same environment also triggers the same `echo-pre-action` Pre-Action Workflow, the earlier instance is terminated, and the later instance continues to run.
254
253
255
254
255
+
## Promotion Hooks in product release
256
+
The **Show/Hide Hooks** toggle button in the Release view displays/hides the [promotion hooks]({{site.baseurl}}/docs/promotions/promotion-hooks/) assigned to the Promotion Flow.
256
257
257
-
<!--- NIMA: how will it be shown in the releases tab? -->
Copy file name to clipboardExpand all lines: _docs/promotions/promotion-components.md
+8-2Lines changed: 8 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -98,12 +98,18 @@ These entities provide additional control and automation, enabling advanced mult
98
98
<td>Users with ABAC permissions</td>
99
99
<td><a href="https://codefresh.io/docs/docs/products/configure-product-settings/">Promotion settings for products</a></td>
100
100
</tr>
101
-
<tr>
101
+
<tr>
102
102
<td><strong>Promotion Workflow</strong></td>
103
-
<td>An Argo Workflow which runs tests and validations during promotion for each environment. Promotion Workflows can include smoke tests, rollback mechanisms, database validation checks, performance checks, and more.</td>
103
+
<td>An Argo Workflow which runs tests and validations during promotion for each application within an environment. Promotion Workflows can include smoke tests, rollback mechanisms, database validation checks, performance checks, and more.</td>
<td>Promotion hooks are configured in Promotion Workflows to run at the start or end of a product release, or at the start or end of promotions in environments. Promotion hooks can include notifications and actions such as sending Slack messages or custom issue-tracking information based on the status of the promotion for release or environment.</td>
<td>Defines promotion behavior for environments by combining Promotion Workflows (tests and validations), with the promotion action such as commits or pull requests.</td>
0 commit comments