# Buildkite trigger step

**URL:** <https://forum.buildkite.community/t/buildkite-trigger-step/3173>\
**Category:** Pipelines\
**Created:** [August 7, 2023, 1:13am UTC](https://forum.buildkite.community/t/buildkite-trigger-step/3173 "2023-08-07T01:13:46Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![surajthakur](https://avatars.discourse-cdn.com/v4/letter/s/96bed5/32.png) [@surajthakur](https://forum.buildkite.community/u/surajthakur)\
**Post date:** [August 7, 2023, 1:13am UTC](https://forum.buildkite.community/t/buildkite-trigger-step/3173/1 "2023-08-07T01:13:46Z")

</div>

Hi Team,

We observed something that we wanted to confirm.

So we are trying the `trigger` step in our build pipeline. Basically the use case is build pipeline triggers the deployment pipeline.  
In the deployment pipeline we have 3 block steps. So that all works fine. But what we noticed is, after the trigger step triggers the deployment pipeline and it reaches the first block step, the build pipeline shows green and notifies “PASSED” and then when you unblock the block step, the build pipeline goes into In-progress again and notifies in Slack of state change and when reaches block step, notifies in slack again of the “PASSED”.

Two things happens

- Build pipeline keeps changing the state. Is this expected?
- On slack notification channel, keep getting passed, creates a bit of noise in the slack channel. How could we avoid that?

Thanks  
Regards,  
Suraj

---

<div class="post-metadata">

**Author:** ![james.s](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/james.s/32/1305_2.png) [@james.s](https://forum.buildkite.community/u/james.s)\
**Post date:** [August 7, 2023, 1:30am UTC](https://forum.buildkite.community/t/buildkite-trigger-step/3173/3 "2023-08-07T01:30:53Z")

</div>

Hello @surajthakur!

Thanks for the message, hope you’ve been well 👋

For your first question - that is indeed the [expected behaviour](https://buildkite.com/docs/pipelines/block-step#block-step-attributes) - and specifically tied to the `blocked_state` attribute of `block` steps. If you _don’t_ specify it in your `block` step, by default the build is set as `passed` when it reaches the corresponding step (the attribute can be set to one of `passed` , `failed` or `running`).

It sounds like you are triggering Slack notifications based on the Notification Services [integration](https://buildkite.com/docs/integrations/slack#adding-a-notification-service) - you could potentially get around it with [conditional](https://buildkite.com/docs/pipelines/notifications#slack-channel-and-direct-messages-conditional-slack-notifications) Slack notifications based on a build state/state of a particualar job’s outcome for example.

Hope that helps 👍

---

<div class="post-metadata">

**Author:** ![surajthakur](https://avatars.discourse-cdn.com/v4/letter/s/96bed5/32.png) [@surajthakur](https://forum.buildkite.community/u/surajthakur)\
**Post date:** [August 7, 2023, 5:50am UTC](https://forum.buildkite.community/t/buildkite-trigger-step/3173/4 "2023-08-07T05:50:24Z")

</div>

Thanks @james.s  
The block step attribute helped.

Is there a ref of colours used by Buildkite Slack app on different build states OR any way to override the colours.  
I am referring to this colour  
 ![image](https://us1.discourse-cdn.com/flex016/uploads/buildkite1/original/2X/6/65629d1a32024cb8a98145ddd649584e0520610e.png)

Thanks

---

<div class="post-metadata">

**Author:** ![james.s](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/james.s/32/1305_2.png) [@james.s](https://forum.buildkite.community/u/james.s)\
**Post date:** [August 7, 2023, 6:28am UTC](https://forum.buildkite.community/t/buildkite-trigger-step/3173/5 "2023-08-07T06:28:40Z")

</div>

Glad to hear it @surajthakur!

Those colours (if you are referring to the _lines_ next to the Buildkite logo describing the message output) are set by the integration itself based on the build’s status as detected - not configurable unfortunately.

Cheers!

---

<div class="post-metadata">

**Author:** ![surajthakur](https://avatars.discourse-cdn.com/v4/letter/s/96bed5/32.png) [@surajthakur](https://forum.buildkite.community/u/surajthakur)\
**Post date:** [August 7, 2023, 6:32am UTC](https://forum.buildkite.community/t/buildkite-trigger-step/3173/6 "2023-08-07T06:32:31Z")

</div>

Thanks @james.s  
All good for now.  
This case can be closed.

---

<div class="post-metadata">

**Author:** ![james.s](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/james.s/32/1305_2.png) [@james.s](https://forum.buildkite.community/u/james.s)\
**Post date:** [August 7, 2023, 6:36am UTC](https://forum.buildkite.community/t/buildkite-trigger-step/3173/7 "2023-08-07T06:36:43Z")

</div>

No worries 👍

Feel free to reach out to us if any other topic or question arises.

Have a awesome day!