title:"How To: SkipStep If Pipeline Is Triggered With Cron"

title:"How To: Skipstep if pipeline triggered with Cron"

description:

group:kb

sub-group:articles

You have a buildthat is triggered bymultiple triggers, and you need to skip a certain step if the pipeline was launched using acron trigger.

You have a buildwithmultiple triggers, and you need to skip a certain step if the pipeline was launched using aCron trigger.

Inyour crontrigger configuration, set a message (e.g., "using cron") in the Message field.

Inthe**Message** field in the Crontrigger configuration, set a message, for example, "using cron".

Utilize the EVENT_MESSAGE variable in your pipeline steps with a conditionlike:

Utilize the`EVENT_MESSAGE` variable in your pipeline steps with a conditionas in the following example:

{% raw %}

{% endraw %}

Thisensures specific steps execute only when thecronjob message is different from"using cron" and pipeline is triggered bycron.

The conditionensuresthatspecific steps execute only when thepipeline is triggered by Cron and the Cronjob message is different fromthe one defined in the Message field ("usingcron" in our example).

[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/)

[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/)

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, volumeresuse and notification behavior to override for the build

* Caching, volumereuse and notification behavior to override for the build

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.

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/).