How can I set up email notifications for builds fails or succeeded and check-in's on TFS 2017?
When the build fails or even if I check in it does not send the email. How to get the email notification?
To configure notifications, simply follow our official tutorial here-- Manage your notifications
For on-premises TFS, you must configure an SMTP server for team members to see the Notifications option from their organization menu and to receive notifications.
Please double confirm your SMTP server which could send the e-mail. Besides, a subscription can be just for you, or if you are a team admin, can be shared by everyone in the team.
If you are setting up a team subscription, try to change to a personal subscription first to check if it works. This will help to narrow down the issue.
Related
I have bought two Twilio phone numbers which are validate and configured by Twilio and WhatsApp.
I created two Conversation Services ("Main Conversation Service" (SID:IS1234) and "Dev Conversation Service" (SID:IS4321)
Both are configured as "Engage in a discussion" Use case configuration.
Both are configured as "Autocreate a Conversation" in the Integration configuration.
Each service has a different phone number configured in the Sender Pool
Each WhatsApp Sender number Endpoint Configuration is configured a "Use Messaging Service (recomended)" with its respective Conversation Service
I have 2 Studio Flows ("WA_MAIN" and "WA_DEV"). In Flex > Manage > Messaging I have 2 WhatsApp addresses pointing each phone number to its respective Studio Flow.
This is the complete configuration, if something important is missing please ask me in the comments.
When I send a whatsapp message to each number the conversation is routed to the correct Studio Flow, but it is managed by the Main Conversation Service (IS1234), which is the older one. I have zero conversations in Dev Conversation Service (IS4321). All previous conversations with my phone number are in "closed" state.
Why is this happening? How can I build to independent environments to work with Conversations API without risking the SLA of Production environment?
This happens because of a Conversation Configuration where you configure the default messaging service that will handle the inbound conversations, you can see it on Conversations > Manager > Defaults.
The Twilio Team advises creating a new account to Homolog or Staging, so it's can be a solution to not affect your production environment.
I hope that it can help you.
We have TFS 2018 on premises. The TFS data was historically migrated from TFS 2010 to TFS 2016 and subsequently to TFS 2018. One of the old projects was set up to send TFS code review notifications to all project team's individual members. All notifications are delivered to correct email addresses except one developer. When I open the project notification sent to me, I can see that notification was sent to misspelled address of this developer. This explains why TFS notification was not delivered to the developer. I don;t know where this address was taken from because her email address looks ok in her TFS profile web page. When she changes her preferred email to another address, notifications are still sent to the wrong misspelled address. Interestingly, the recently created TFS projects do not have this problem. All notifications are sent to her email address which matches her AD address. I am puzzled. Is notification email address is stored on a project level in TFS? How can I fix this? Can anyone please help? Thank you.
Unfortunately, I could not find a way to correct address from TFS web portal.Therefore, I just searched all TFS databases for misspelled email address. I found two columns were misspelled address was stored: TFSDefaultCollection.tbl_EventSubscription.Address and TFSDefaultCollection.tbl_EventNotification.NotificationMetadata. Both tables were updated with correct email address.
In Team Foundation Server, how can one access their notifications through the UI without having to get them through email? I.e., kind-of like GitHub's /notifications page.
TFS version: 16.131.27701.1
TFS notifications without emails
Sorry for any inconvenience.
I am afraid there is no such out-of-the-box way to access notifications through the UI instead of email.
At this moment, there is only an extensible plugin for Team Foundation Server that sends notifications to Slack not for the web UI:
TfsNotificationRelay
You could add your request for this feature on our UserVoice site (https://developercommunity.visualstudio.com/content/idea/post.html?space=21 ), which is our main forum for product suggestions. Thank you for helping us build a better Azure DevOps.
Hope this helps.
I recently integrated my Jenkins with Microsoft Teams for notifications. Through webhook, I am able to push the notifications to the channels under my Team.
Refered -
https://wiki.jenkins.io/display/JENKINS/Office+365+Connector+Plugin
Now the scenario is I need to send an attachment like build log, etc to be sent out from Jenkins to Teams as like Email editable plugin do.
Can anyone advise?
Connectors only support MessageCard. There is no option to send attachments using Connectors.
I cannot see Webhook function on Bitbucket server. The view is different from the Bitbucket on Cloud. The main goal of mine is i am trying to integrate Slack to get all updates from Bitbucket. Could anyone help me figure this out?
To do this you will need to install the 'Slack Notifications Plugin'.
BitBucket server works on a 'add additional functionality as you need it' model, whereas BitBucket cloud has to cater to a large number of possible user needs where users don't have admin to install the plugins themselves.
To setup: navigate to the custom integrations tab on the Apps admin page in Slack, then select 'Incoming Webhooks', 'Add configuration', choose a channel and hit add. You should now have a webhook URL copy this. (you can come back and change the appearance of your webhook user later on or edit it now)
Take the URL you copied, and go to the admin page for your repository in BitBucket server, click 'Slack settings'. Select the events you want to receive messages for, if you want to receive notifications for commits then tick the Push notifications option. Enter the channel name you want to post to including the # e.g. #git and paste in your Webhook URL. Save.
Now when you push a commit to BitBucket you should get a message in the specified Slack channel.
The official Bitbucket Server integration for Slack, developed by Atlassian, is now released with Data Center support. You can try it out right now.
Disclaimer: I work for Atlassian.