Closed asheynkman closed 2 years ago
Hi @asheynkman. As we resolved this via email, I'll share the conclusions for others with the same issue below:
This issue relates to the Coveralls Notifications feature, found in [Your Repo] > Settings > Notifications, which enable your Coveralls repo to send coverage updates via notifications to various services, including Email, Slack, (Generic) Webhook, etc.
Notably, this issue is not related to the Parallel Builds Webhook feature (aka. the webhook endpoint of the Coveralls API), which is discussed here.
Coveralls currently supports sending notifications to these services:
We do not currently support the Microsoft Teams service.
Custom support for such as service would probably entail data formatting to support a proprietary messaging standard, which could include authorization headers, required fields (like target channel), etc.
The best we can offer at this time to to use the most generic notification, the Webhook Notification, which sends simple JSON to a designated endpoint, and choose as your endpoint an iPaaS platform, such as Zapier.com, that will connect with Microsoft Teams.
Here's how that would look using a sample Coveralls project and Zapier.com account:
1) Create a New "Zap" with a Zapier Webhook Trigger:
2) Choose Microsoft Teams as the next step, the Action:
Examining the trigger payload gives you an idea about the structure of the JSON object Coveralls is sending.
3) Choose Send Channel Message as the Action and select the Channel where you want the message to go:
We're not affiliated with Zapier.com in any way. It simply has a free tier, but you have many alternative services like this to choose from.
This issue has been automatically marked for closure because it has not had recent activity. It will be closed if no further activity occurs. If your issue is still active please add a comment and we’ll review as soon as we can. Thank you for your contributions.
MS Teams WebHooks Integrations keep throwing error 400. How can you make it work?