admin管理员组

文章数量:1346292

On our on-prem Azure Devops Server 2020 we have a build pipeline that runs every evening at 23:00. We would like to receive an email at the end of the build. For some reason we do not receive mails. We have configured this with delivery option 'Team Preference', with delivery setting the a team-address.

Can someone explain why this does not work? A notification with the delivery option 'Custom e-mail address' seams to work.

When trying to investigate I was using this page about diagnostics:

I could found log entries for the 'event matching'

"SubscriptionTopNotificationGenerators":{"4397":1,"740":1,"4393":1,"4395":1,"4396":1},"SubscriptionTopTimeConsumers":{"4397":8,"4395":5}

In the logs for the 'diagnostic logs for notification delivery' I don't see only an error with subscriptionID 740: 'message":"Altered event is null for event 5447742 of type BuildCompletedEvent". Could this block the other subscriptions?

Does anyone know how these diagnostics logs work or how to diagnose what is going on here?

On our on-prem Azure Devops Server 2020 we have a build pipeline that runs every evening at 23:00. We would like to receive an email at the end of the build. For some reason we do not receive mails. We have configured this with delivery option 'Team Preference', with delivery setting the a team-address.

Can someone explain why this does not work? A notification with the delivery option 'Custom e-mail address' seams to work.

When trying to investigate I was using this page about diagnostics: https://learn.microsoft/en-us/azure/devops/anizations/notifications/use-subscription-logging?view=azure-devops-2020

I could found log entries for the 'event matching'

"SubscriptionTopNotificationGenerators":{"4397":1,"740":1,"4393":1,"4395":1,"4396":1},"SubscriptionTopTimeConsumers":{"4397":8,"4395":5}

In the logs for the 'diagnostic logs for notification delivery' I don't see only an error with subscriptionID 740: 'message":"Altered event is null for event 5447742 of type BuildCompletedEvent". Could this block the other subscriptions?

Does anyone know how these diagnostics logs work or how to diagnose what is going on here?

Share Improve this question asked 2 days ago RemkopRemkop 1331 silver badge7 bronze badges
Add a comment  | 

1 Answer 1

Reset to default 0

The 1st screenshot shows the subscriptionId(beside Edit Subscription) is 4395 not 740, typically the error from 740 will not affect target subscription 4395.

If there's no error from the two diagnostic logs, you can follow below steps for a check:

  1. Go to Collection settings-> Global notifications -> Statistics page, check if the notification subscription is listed.

Notifications value: confirm it will increase once new schedule run completes, it ensures the event is caught. If the number is not increased, edit the subscription, try to add more clause to catch, eg:

Event Type: Should be Build Completed.

In addition, on this page, you can also try to find the subscription which has id 740, disable it, check again if the target subscription is working then.

  1. If event is caught successfully above, it could be caused by the email.

    a. Check junk box of the email if the notification email is sent to.

    b. If it's OK, try to check the email can receive the email. Also you can try to change a new email in subscription delivery setting for test.

c. Confirm the SMTP server is correctly configure on the DevOps server, reconfigure it if needed.

本文标签: tfsEmail Notifications in Azure devops Server on a scheduled buildStack Overflow