# Triggers on subscriptions

**URL:** <https://forum.buildkite.community/t/triggers-on-subscriptions/361>\
**Category:** Features Requests\
**Created:** [March 8, 2019, 10:18pm UTC](https://forum.buildkite.community/t/triggers-on-subscriptions/361 "2019-03-08T22:18:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![AnthonyWC](https://avatars.discourse-cdn.com/v4/letter/a/dfb087/32.png) [@AnthonyWC](https://forum.buildkite.community/u/AnthonyWC)\
**Post date:** [March 8, 2019, 10:18pm UTC](https://forum.buildkite.community/t/triggers-on-subscriptions/361/1 "2019-03-08T22:18:49Z")

</div>

Currently trigger build supports only a push style where one need to explicitly define other pipeline to trigger. This style is limiting; it would be good if trigger build also support subscription based type of syntax where other pipeline can simply reference the original pipeline to get trigger.

---

<div class="post-metadata">

**Author:** ![azz](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/azz/32/462_2.png) [@azz](https://forum.buildkite.community/u/azz)\
**Post date:** [March 9, 2019, 10:50am UTC](https://forum.buildkite.community/t/triggers-on-subscriptions/361/2 "2019-03-09T10:50:41Z")

</div>

Something like this?

```auto
triggers:
  - pipeline: "some-pipeline-slug"
    event: "started|blocked|completed|succeeded|failed"

steps:
  - command: "buildkite pipeline upload"

```

---

<div class="post-metadata">

**Author:** ![samuelkdavis\_mcf](https://avatars.discourse-cdn.com/v4/letter/s/ad7895/32.png) [@samuelkdavis\_mcf](https://forum.buildkite.community/u/samuelkdavis_mcf)\
**Post date:** [November 7, 2019, 8:31pm UTC](https://forum.buildkite.community/t/triggers-on-subscriptions/361/3 "2019-11-07T20:31:49Z")

</div>

Builds being able to listen to events would be really handy. This could keep the pipeline event driven.

Triggering based on multiple scenarios would also be helpful if relying on multiple conditions to trigger a deploy etc.

Jenkins supports this

First build:

> <https://github.com/samuelkdavis/Questionnaire/blob/master/Jenkinsfile#L1-L21>

Second build triggered from first build:

> <https://github.com/samuelkdavis/TestJenkinsBlueOceanTrigger/blob/master/Jenkinsfile#L4>