Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Post to more than one channel #2

Open
asbjornu opened this issue Nov 5, 2014 · 5 comments
Open

Post to more than one channel #2

asbjornu opened this issue Nov 5, 2014 · 5 comments

Comments

@asbjornu
Copy link

asbjornu commented Nov 5, 2014

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.

@asbjornu asbjornu changed the title More configuration options Post to more than one channel Nov 5, 2014
@mikecole
Copy link

+1 for this feature.

@irobinson
Copy link
Contributor

This is definitely on the radar - haven't had the opportunity to dig into it yet but we could use this functionality as well.

@koraybalci
Copy link

Any updates on this issue?

@eljobe
Copy link
Contributor

eljobe commented Sep 23, 2016

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.

@aclark09
Copy link
Contributor

I like it. Shouldn't affect users who decide to not use the feature and keep using the old pattern.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants