nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is there a way to create a slack subscription based off of a specific build rule?

Vincent Jong

So we have a test repo that has a variety of pipelines based on test type, etc. We're using the slack subscription plugin and that seems every pipeline when run fires a message to the slack channel. Is there a way to add another subscription that only fires when a specific pipeline is run to another channel?

Sub 1 - repository wide, to slack_channel_1

can have a

Sub 2 - pipeline 5, to slack_channel_2

Accepted answers

All comments

Theodora Boudale

Hi Vincent,

I assume you are using Atlassian's integration with Slack and you have set up subscriptions from Repository settings > SLACK Settings?

If so, that should be possible as long as this specific pipeline runs on a certain branch. For example, it could be the default pipeline running on this specific branch, let's say develop, or a branch pipeline for develop branch.

You could then add a second subscription that sends messages to a different channel, and in that subscription remove the repository-wide notifications and add the branch develop with the relevant notifications for pipeline.

Please keep in mind that when a build runs on develop, the notifications will be sent to both channels (since the first channel has the repository-wide notifications set up).

Is this what you are looking for?

Kind regards,
Theodora

Vincent Jong

Repository settings > SLACK Settings? - correct.

Sort of... our test E2E pipelines all run against the main branch, so it sounds like you're saying what we want is not possible as set up. Is it possible to craft a workaround? You're correct that a run on this would sent to both channels but that's ok as the channels are set to different audiences...

Vincent Jong

Like maybe:

Create a new branch to run the pipeline against
In the new branch, pull from main branch when it has merged changes, or when the pipeline on the new branch is called to run?

Theodora Boudale

Hi Vincent,

Thank you for your answer.

You mention that your pipelines all run against the main branch. In the yml file you can specify only one pipeline for a certain branch (that runs on a branches definition). Are your multiple pipelines custom ones (see link below on what custom pipelines are) that you trigger manually or on schedule?

https://support.atlassian.com/bitbucket-cloud/docs/pipeline-start-conditions/#Custom--manual--pipelines

I'm asking to better understand your use case and then create a feature request for our development team to consider and also to understand if the workaround you suggested would work.

If you indeed have custom pipelines, then the workaround with the new branch would work. You would need to merge the changes from the main branch before running the pipeline, to ensure the new branch has the latest changes of main branch. It would be good to communicate this set up with the rest of your team, to avoid any confusion about the purpose of this branch.

Kind regards,
Theodora

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud