Feature request: multiple Slack channels

[maiamcc]

Is there currently a way to have a project send notifications to more than one Slack channel? If not, consider this a feature request!

[wimdeblauwe]

The docs state that you can use comma separated values:

Enter the channel names to which notifications should be sent. Note that this can include names of channels OR channel id numbers, e.g. "#builds", and that multiple values may appear comma separated. While names are more readable, channel ids will not change over time and are therefore more resilient.

(emphasis mine)

[zekedroid]

That's awesome however how would one set up two separate post-build actions for the Slack plugin? Consider having one action which pushes the much more important build failures to a general channel, and ALL build statuses to a jenkins-dump channel. Is there a way to do that?

[samrocketman]

@zekedroid see #41

[samrocketman]

@maiamcc As @wimdeblauwe mentions posting to multiple channels is documented. It actually accepts multiple characters as channel separators such as: comma, semicolon, space.

See

slack-plugin/src/main/java/jenkins/plugins/slack/StandardSlackService.java

Line 31 in 3558429

this.roomIds = roomId.split("[,; ]+");

[filipre]

I am having troubles following this. This is what our settings look like

If I try to add another channel using a , it tells me that this channel does not exist. Does this only work with slackSend ?

[darthsteven]

@filipre I think you're after the 'Project Channel' setting on the Jenkins plugin configuration form:

This works nicely for me, and it doesn't seem to matter what the Slack side is set to :)

[jonathanappel]

@darthsteven that setting is global to jenkins correct? I can't have different pipelines posting to different channels?

[samrocketman]

@jonathanappel it is a global default but can be overridden in either freestyle jobs or pipeline jobs.

For pipeline jobs, refer to the slackSend step code.

Here's an example pipeline posting a slackSend status for a build. Note: this code is really old and I don't write pipeline code like that anymore. I never bothered to update this project with my latest code style (I have no near term plans to update it). But it gives you an idea on usage.