Merge pull request #867 from maryiaCodefresh/maryia-howto-cron

maryiaCodefresh · web-flow · commit 7aa4f672b929 · 2023-12-14T16:21:42.000+02:00
Created skip-test-if-pipeline-is-triggered-with-cron.md
diff --git a/_docs/kb/articles/skip-test-if-pipeline-is-triggered-with-cron.md b/_docs/kb/articles/skip-test-if-pipeline-is-triggered-with-cron.md
@@ -0,0 +1,52 @@
+---
+title: "How To: Skip step if pipeline triggered with Cron"
+description: 
+group: kb
+sub-group: articles
+toc: true
+kb: false
+ht: true
+common: false
+categories: [Pipelines]
+support-reviewed: 2023-12-12 MB
+---
+
+## Overview
+
+You have a build with multiple triggers and you need to skip a certain step if the pipeline was launched using a Cron trigger.
+
+## Details
+
+### Configure Cron trigger message
+
+In the **Message** field of the Cron trigger configuration settings, set a message, for example, "using cron".
+
+### Implement Conditional Step
+
+Use the `EVENT_MESSAGE` variable in your pipeline steps with a condition as in the following example:
+
+{% raw %} 
+
+    ```yaml
+    Freestyle:
+      title: Running alpine image
+      type: freestyle
+      arguments:
+        image: 'quay.io/codefreshplugins/alpine:3.8'
+        commands:
+          - echo "Displayed only when triggered by cron"
+      when:
+        condition:
+          all:
+            validateTriggerType: '"${{EVENT_MESSAGE}}" != "using cron"'
+    ```
+
+{% endraw %}
+
+The condition ensures that specific steps execute only when the pipeline is triggered by Cron, _and_ if the Cron job message differs from the one defined in the Message field (`using cron` in our example).
+
+## Related Items
+[Triggers in pipelines]({{site.baseurl}}/docs/pipelines/triggers/)  
+[Cron trigger event variables]({{site.baseurl}}/docs/pipelines/triggers/cron-triggers/#cron-event-payload)  
+[Conditional execution of steps]({{site.baseurl}}/docs/pipelines/conditional-execution-of-steps/)  
+[Freestyle step]({{site.baseurl}}/docs/pipelines/steps/freestyle/)  
diff --git a/_docs/pipelines/triggers/cron-triggers.md b/_docs/pipelines/triggers/cron-triggers.md
@@ -72,7 +72,7 @@ There are two parts to creating a Cron trigger in the UI:
 1. (Optional) Selecting additional options:  
   * Git trigger event to simulate when the Cron trigger timer is activated. The pipeline is populated with the information from the Git repo such as the repo URL, branch name, latest commit information, including the date and author of the commit.
   * Variables to populate for the build
-  * Caching, volume resuse and notification behavior to override for the build  
+  * Caching, volume reuse and notification behavior to override for the build  
 
 
 
@@ -198,6 +198,9 @@ For example, `@every 1h30m10s` would indicate a schedule that triggers every 1 h
 >**NOTE:**  
 The interval does not take the runtime of the job into account. For example, if a job takes three minutes to run, and it is scheduled to run every five minutes, it will have only two minutes of idle time between each run.
 
+### Conditional triggers for Cron jobs
+Take a look at our Knowledge Base how-to: [Skip pipeline step if triggered by Cron job]({{site.baseurl}}/docs/kb/articles/skip-test-if-pipeline-is-triggered-with-cron/).
+
 ## Cron triggers with Codefresh CLI
 
 >**NOTE**:  
