- \n
- Build success:\n
- \n
- Always<\/b>: When your app builds successfully<\/li>\n
- Only if previously failed<\/b>: When your app has successfully built after one or more failed builds<\/li>\n
- Never<\/b>: You will not receive notifications for build success<\/li>\n<\/ul>\n<\/li>\n
- Build failure:\n
- \n
- Always<\/b>: When your app fails to build<\/li>\n
- Only if previously successful<\/b>: When your app has failed to build after one or more successful builds<\/li>\n
- Never<\/b>: You will not receive notifications for build failure<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
- \n
- \u26a0 Crashes<\/b>: When a crash group is created<\/li>\n
- \ud83d\udd31 Distribute<\/b>: When a new\u00a0version is released<\/li>\n<\/ul>\n
By default, email notifications are sent only when a new version is released. Whether you’re an admin, app developer, or tester, it’s important to be notified immediately when a new version is released to testers or to the store. For admins or app developers involved in the Continuous Integration, Delivery and Deployment process, it’s useful to set up email and custom webhook notifications for build and distribute.<\/p>\n
Setting up App Center Notifications<\/h2>\n
To get started, you need to have App Center\u2019s Build service set up. I\u2019ve onboarded the SmartHotel360<\/a> mobile demo app to our Build service by connecting my Visual Studio Team Services source code repository and triggering a build on the `Release` branch on every push. You can read David Sanchez\u2019s blog post to learn more about setting up a build for the SmartHotel360 app<\/a>.<\/p>\n
Set up Build Status Notifications<\/h3>\n
- \n
- \n
- \n
- Go to the app for which you\u2019d like to configure email and webhook status notifications<\/li>\n
- Navigate to the app\u2019s Settings<\/strong>, and:<\/span>\n
- \n
- To configure your email notifications<\/strong>, click Email notifications and select the events to trigger an email notification. Personally, I’m interested in when my build has succeeded or failed and when a crash group has happened.<\/span><\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n
![\"\"](\"https:\/\/devblogs.microsoft.com\/appcenter\/wp-content\/uploads\/sites\/3\/2017\/10\/1-emailNotifications-1024x657.gif\")
\n\nHere is the documentation on how to configure your email notifications<\/a>.<\/p>\n
b. To configure a webhook, click New Webhook<\/strong> and enter your webhook name<\/strong>, URL<\/strong>, and select the events<\/strong> to trigger the\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0webhook alerts.<\/p>\n
In the example below, I\u2019ve configured a Slack webhook:<\/p>\n
![\"\"](\"https:\/\/devblogs.microsoft.com\/appcenter\/wp-content\/uploads\/sites\/3\/2017\/10\/2-createSlackWebhook-1024x653.gif\")
<\/p>\nHere is the documentation on how to set up a webhook<\/a> and how to obtain the Slack<\/a> and Microsoft Teams<\/a> webhook URL.<\/p>\n
3. Now, let\u2019s kick off a new build!\nClick Build<\/strong>, select the gear icon<\/strong> of the branch you\u2019d like to build, and click `Save & Build`.<\/p>\n
![\"\"](\"https:\/\/devblogs.microsoft.com\/appcenter\/wp-content\/uploads\/sites\/3\/2017\/10\/3-triggerBuild-1024x649.gif\")
\n<\/p>\n
<\/p>\n
4. After the build is completed, you’ll receive a build status email and webhook notification with the build details and a link to view the\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0build.\nHere’s an example of an email with a failed build:<\/p>\n
![\"\"](\"https:\/\/devblogs.microsoft.com\/appcenter\/wp-content\/uploads\/sites\/3\/2017\/10\/4-buildFailed-1024x963.png\")
<\/p>\n\nYou can click on the View<\/strong> link to view the build output details, distribute the app, and download the build or logs in App Center.<\/p>\n
![\"\"](\"https:\/\/devblogs.microsoft.com\/appcenter\/wp-content\/uploads\/sites\/3\/2017\/10\/5-openEmailBuildLink-1024x654.gif\")
<\/p>\nYou’ll now be notified of your build status and can @ mention or email your developers to quickly fix failed builds before they reach more users. Awesome, crisis averted!<\/span><\/p>\n
- \n
- \n
- \n
- Webhook Notification\n
- \n
- \n
- \n
- In Slack\n
![\"\"](\"https:\/\/devblogs.microsoft.com\/appcenter\/wp-content\/uploads\/sites\/3\/2017\/10\/6-openSlackWebhookBuildLink-1024x653.gif\")
\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
<\/p>\n
- \n
- In Microsoft Teams\n
![\"\"](\"https:\/\/devblogs.microsoft.com\/appcenter\/wp-content\/uploads\/sites\/3\/2017\/10\/7-openMSTeamsWebhookBuildLink-1024x651.gif\")
\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
<\/p>\n
Get started and send us your feedback!<\/h2>\n
Log in to App Center<\/a>\u202f(or\u202fcreate your free account\u202ftoday<\/a>) and start kicking off builds, toggling your email notification settings, and configuring webhooks. We\u2019re keen to hear what you\u2019d like to see next, so send us your feedback on what worked (and what didn\u2019t) for you.<\/p>\n
Enjoy, and let’s get building! \ud83d\ude0a<\/p>\n","protected":false},"excerpt":{"rendered":"
We\u2019re excited to announce the launch of build status notifications for Visual Studio App Center! Based on your feedback, we know some of you are customizing your build definitions to notify your team about the build status. Now you can say goodbye to these custom steps and simply use the email and webhook notifications feature […]<\/p>\n","protected":false},"author":660,"featured_media":38034,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[16],"tags":[],"class_list":["post-4095","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-mobiledev"],"acf":[],"blog_post_summary":"
We\u2019re excited to announce the launch of build status notifications for Visual Studio App Center! Based on your feedback, we know some of you are customizing your build definitions to notify your team about the build status. Now you can say goodbye to these custom steps and simply use the email and webhook notifications feature […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/appcenter\/wp-json\/wp\/v2\/posts\/4095","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/appcenter\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/appcenter\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/appcenter\/wp-json\/wp\/v2\/users\/660"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/appcenter\/wp-json\/wp\/v2\/comments?post=4095"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/appcenter\/wp-json\/wp\/v2\/posts\/4095\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/appcenter\/wp-json\/wp\/v2\/media\/38034"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/appcenter\/wp-json\/wp\/v2\/media?parent=4095"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/appcenter\/wp-json\/wp\/v2\/categories?post=4095"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/appcenter\/wp-json\/wp\/v2\/tags?post=4095"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- In Microsoft Teams\n
- In Slack\n
- \n
- Webhook Notification\n
- \n
- To configure your email notifications<\/strong>, click Email notifications and select the events to trigger an email notification. Personally, I’m interested in when my build has succeeded or failed and when a crash group has happened.<\/span><\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n
- \ud83d\udd31 Distribute<\/b>: When a new\u00a0version is released<\/li>\n<\/ul>\n
- Only if previously successful<\/b>: When your app has failed to build after one or more successful builds<\/li>\n
- Only if previously failed<\/b>: When your app has successfully built after one or more failed builds<\/li>\n
- Always<\/b>: When your app builds successfully<\/li>\n