Nov 13, 2020 by Ryan Cartwright
Microsoft Teams notification support is now available in Spinnaker 1.23.0.
An issue was opened in the Spinnaker github repo on June 9th to add support MS Teams to Echo. But wait, there was a very old issue opened back in 2016, when Spinnaker was first open sourced. Thanks to Metri Dmitriev for opening a new issue.
During the Spinnaker Gardening Days summer edition that took place during Spinnaker.Live, one of the proposals was to add support for Microsoft Teams. Thanks to Victor Odusanya, Ige Adetokunbo, Vishal Nair, Ryan Pei, and Daniel Peach for your contributions to this plugin.
Fast forward a few months, the project is complete thanks to additional contributions from Lead Technology Architect, Jeffrey Coe, from Cerner. Cerner Corporation is an American supplier of health information technology services, devices, and hardware. They were an early adopter of Spinnaker using for DC/OS deployments. Read their blog here and watch their video here.
Per the documentation on Spinnaker.io:
To enable Microsoft Teams support, add the following statement to the
microsoftteams: enabled: true
Spinnaker supports sending notifications to Microsoft Teams using Incoming Webhooks.
To create a custom incoming webhook in Teams, follow the instructions provided here: Add an incoming webhook to a Teams channel
When configuring a Microsoft Teams notification, enter the full incoming webhook URL in the
Teams Webhook URL text box.
This is a great example of the collaboration that takes place in the Spinnaker community. Join the Spinnaker slack workspace to get involved in the project. You can also become a stargazer or watcher of the Spinnaker Github project. Please join the Azure SIG if there are other Microsoft integrations that you want to see added to Spinnaker.
And if you’re interested in knowing more about Spinnaker plugins, check out this article for creating your own custom stage in Spinnaker. You can now add any kind of task to your Spinnaker pipeline via a custom stage plugin.
Software deployment processes differ across organizations, teams, and applications. The most basic, and perhaps the riskiest, is the “big bang deployment.” This strategy updates all nodes within the target environment simultaneously with the new software version. This deployment strategy causes many issues, including potential downtime or other issues while the update is in progress. It […]
Read more →
Multi-target deployments can feel tedious as you deploy the same code over and over to multiple clouds and environments — and none of them in the same way. With an automatic multi-target deployment tool, on the other hand, you do the work once and deliver your code everywhere it needs to be. Armory provides an […]
Read more →
KubeCon+CloudNativeCon EU is one of the world’s largest tech conferences. Here, users, developers, and companies who have and intend to adopt the Cloud Native standard of running applications with Kubernetes in their organizations come together for 5 days. From May 16-20, 2022, tech enthusiasts will congregate both virtually and in person in Valencia, Spain to […]
Read more →