# Run pipeline on Push and Cron

**URL:** https://drone.discourse.group/t/run-pipeline-on-push-and-cron/9583
**Category:** Drone Support
**Created:** [June 5, 2020, 2:30am UTC](https://drone.discourse.group/t/run-pipeline-on-push-and-cron/9583 "2020-06-05T02:30:13Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![zaggash](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/zaggash/32/3624_2.png) [@zaggash](https://drone.discourse.group/u/zaggash)
#### Post date: [June 5, 2020, 2:30am UTC](https://drone.discourse.group/t/run-pipeline-on-push-and-cron/9583/1 "2020-06-05T02:30:14Z")

</div>

Hello discourse 🙂

I’m trying to trigger a pipeline either on push or by a specific cron.

Here is my snippet:  
kind: pipeline  
type: docker  
name: pipe1

```
    trigger:
      event:
      - push
      - cron
      cron:
      - my_cron_job_name

```

I read that to trigger all events must be true, so does it mean one pipeline equal one event ?  
I’m confused.

---

<div class="post-metadata">

### Author: ![miiimooo](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/miiimooo/32/2787_2.png) [@miiimooo](https://drone.discourse.group/u/miiimooo)
#### Post date: [October 28, 2020, 2:44pm UTC](https://drone.discourse.group/t/run-pipeline-on-push-and-cron/9583/2 "2020-10-28T14:44:22Z")

</div>

@zaggash you should use the include syntax [see here](https://docs.drone.io/pipeline/docker/syntax/trigger/#by-event) for details, but something like this should work:

```auto
     trigger:
       
      include:
      - push
      - cron

```

The cron job name is not possible and I don’t know whether you can specify the `target` (hourly, weekly, etc)

---

<div class="post-metadata">

### Author: ![zaggash](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/zaggash/32/3624_2.png) [@zaggash](https://drone.discourse.group/u/zaggash)
#### Post date: [October 28, 2020, 2:57pm UTC](https://drone.discourse.group/t/run-pipeline-on-push-and-cron/9583/3 "2020-10-28T14:57:58Z")

</div>

Yeah I figured.  
The problem is you cannot specify the cron name.  
If you have multiple of them, the pipeline will be triggered for every cron setup on the repo.

So I had to change my logic.  
Not a big deal, but it would have been a nice feature.
