It would be nice to have notifications go to slack instead of email etc.
It seems you can set up Slack to work via your XMPP publisher (https://get.slack.help/hc/en-us/articles/201727913-Connecting-to-Slack-over-IRC-and-XMPP) but Continua doesn’t have the option to specify a channel/room in the settings.
I’d like to see a slack notification publisher added and be able to specify a channel when creating a subscription. This way, notifications for one project can be directed to it’s own channel to notify subscribed members while notifications for another project can be sent to another slack channel.
Regards,
Sean
Hi Sean,
Thank you for this feature request. We have had a plan to overhaul the notifications system, so that we can add new publisher types (such as Slack), for some time now. This does, however, require a significant rethink of the notifications architecture and therefore the feature has never reached the top of the queue. All I can do at the moment is bump up the priority.
Yes I do remember you guys wanting to rework this roughly two years ago - https://www.finalbuilder.com/support/forums/aft/13479 . This is one of the most viewed topics under the Continua forum.
If it’s any help, Slack provides a web-hook which you can simply post a JSON packet to which literally has a single property called “text” to create a message. More info at https://api.slack.com/incoming-webhooks#customizations_for_custom_integrations
Looking forward to any updates on this but won’t hold my breath
Hi Sean
Every time the notification rework task gets near the top of the list, something else more urgent comes along and pushes it back down the list. We have very limited resources (ie developers) and everything we do comes with an oportunity cost (what else are we not doing as a result).
FWIW, adding slack support etc is not difficult, it’s all the plumbing and architecture and changes to existing setups that will take the time. We’ll get to it one day, hopefully it won’t take another 2 years though!
No problems, I know what it’s like. More of a friendly reminder than anything else Sean
I only just upgraded to the latest version this morning and noticed this feature had been added - http://wiki.finalbuilder.com/display/continua/HTTP+Request
Thank you!
It works perfectly and here is an example of the JSON body I’m using for anyone else who’s interested.
{
“username”: “Continua CI”,
“channel”: “#buildanddeploy”,
“attachments”: [
{
“color”: “good”,
“title”: “Success”,
“text”: “$Project.Name$/$Configuration$ build completed successfully for branch $Source.RepoName.BranchName$ (Changeset Id: $Source.RepoName.BuiltChangeset.Id$).\n\nThe user responsible for this changeset is $Source.RepoName.BuiltChangeset.RepositoryUsername$”,
“mrkdwn_in”: [
“text”,
“pretext”
]
}
]
}