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
* Review[Assigning Promotion Flowsand triggers to products to products]({{site.baseurl}}/docs/products/promotion-flow-triggers/)
183
183
184
184
185
185
#####How to
@@ -189,7 +189,7 @@ Automate and orchestrate promotions across different environments for the produc
189
189
1. From the list of Promotion Flows, select a predefined Flow for the product.
190
190
1. Define the conditions to match and trigger the Promotion Flow:
191
191
1.**Property**: The property to monitor for changes, based on either the text description associated with the commit message (`commitMessage`), or the commit hash generated by Git (`gitRevision`).
192
-
`commitMessage` can be a single or multiple words, ora set of words.
192
+
`commitMessage` can be a single or multiple words, orphrases with or without wildcards (`*`).
193
193
1.**Operator**: The operator to apply when matching the Property, based on inclusion or exclusion, with or without wildcards.
194
194
`In`: Checks if the commit message or Git revision <i>includes</i> the specified value or any value within a set of values. Commit messages can include
195
195
`NotIn`: Checks if the commit message or Git revision <i>does not include</i> the specified value or any value within a set of values.
Copy file name to clipboardExpand all lines: _docs/products/promotion-flow-triggers.md
+12-8Lines changed: 12 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,14 @@
1
1
---
2
-
title:"Selecting Promotion Flowsfor products"
3
-
description:"Select Promotion Flows and configuretriggerstoorchestrate product promotions"
2
+
title:"Assigning Promotion Flowsand triggers to products"
3
+
description:"Select Promotion Flows and configuretheir trigger conditionstooptimize product promotions"
4
4
group:products
5
5
toc:true
6
6
---
7
7
8
8
##Promotion Flows for products
9
9
A Promotion Flow in Codefresh GitOps defines the steps, validations, and conditions required to promote a product and its applications from one environment to another.
10
10
11
-
By selecting Promotion Flows for a product you can choose the most relevant flows for its deployment strategy.By configuring trigger conditions for each Flow, you can structure promotions for the product, tailored to its needs, improving deployment consistency and efficiency.
11
+
By selecting Promotion Flows for a product you can choose the most relevant flows for its deployment strategy.By configuring trigger conditions for each Flow, you can structure promotions for the product, tailored to its needs, improving deployment consistency and efficiency.
12
12
13
13
#####Benefits of Promotion Flows with triggers tailored for products
14
14
@@ -25,18 +25,22 @@ By selecting Promotion Flows for a product you can choose the most relevant flow
25
25
Arrange the Promotion Flows in a prioritized order to control the sequence in which they are evaluated and executed.
Select one or more Promotion Flows for the product, and then configure custom conditions to trigger each of the flows.
31
31
See also[Product CRD](#promotion-crd).
32
32
33
-
#####Commit messages & Git revisions
33
+
##Commit messages & Git revisions
34
34
You can monitor changes based on the commit message (`commitMessage`) or the Git revision (`gitRevision`).
35
-
The commit message can include single words, multiple words, or phrases. For example,`hotfix` or`update image to v1.2`. There are no restrictions on commit messages.
36
-
37
35
36
+
###Commit message formats
37
+
There are no restrictions on commit messages. The commit message can include:
38
+
* A single word, for example,`hotfix`
39
+
* Multiple words, for example,`hotfix``upgrade`
40
+
* Phrases with or without wildcards (`*`), for example,`refactor Helm chart values`,`update image to v1.*`,`[GitOps] Update image tag to v2.0`.
41
+
38
42
39
-
#####Matching operators for filtering commits
43
+
###Matching operators for filtering commits
40
44
Operators define how commit messages or Git revisions are matched:
41
45
*`In`: Includes the specified value or any value from a set.
42
46
*`NotIn`: Excludes the specified value or any value from a set.