Open asbjornu opened 9 years ago
+1 for this feature.
This is definitely on the radar - haven't had the opportunity to dig into it yet but we could use this functionality as well.
Any updates on this issue?
I'd like to suggest a way to implement this. Allow the Slack Notificator to be configured without specifying a channel. That is, make the field optional. Then treat a special parameter on the build configuration or project teamcity.slack.channel
as the channel to which notifications should be sent when events related to that build configuration or project are observed by the Notificator. There is a reference to the build which is passed into the Notificator for most build events, and the parameters can be read from that object. If a channel is specified in both the Notificator's configuration and as a parameter, the channels would be deduplicated and all channels would be notified.
If that sounds like a good plan, I can take a stab at implementing once I get some of the other features I'm working on to a good place.
I like it. Shouldn't affect users who decide to not use the feature and keep using the old pattern.
This is really a problem with how notifications are set up in TeamCity and how they are user specific, but it would be nice if it was possible to configure the notifier to post to more than one channel. We have one channel per project (sort of) and it would be awesome to be able to create one notification rule per project and have that connected to the appropriate channel, somehow.