仅使用VSTS的Build & Release功能，GitLab外部用户能否收到构建通知？
Great question! Let's break this down clearly based on how Azure DevOps (formerly VSTS) and GitLab integrate, especially with your free user license setup:
First, the core point: Users without an Azure DevOps account/license can't receive native Azure DevOps build/release notifications by default. Azure DevOps' built-in notification system is tied to users who have been granted access to your project (which requires a license or being added as a guest, and your free 5-user limit applies here).
But there are workarounds to get full build/release error notifications to those GitLab users, and they're pretty straightforward:
Custom email notifications from your pipeline
You can add a step directly in your Azure DevOps build or release pipeline that sends an email with complete error details when a failure occurs. Here's how to approach it:- Use the built-in
Send Emailtask (you'll need to configure an SMTP server—like your company's internal SMTP, Office 365, or a third-party service) - Or write a simple PowerShell/Bash script that calls an email API (e.g., your company's internal mail service)
- Include key details in the email: build/release number, error message snippets, direct link to the build/release logs (use Azure DevOps variables like
$(Build.LogUri)or$(Release.ReleaseUri)), and the commit/branch that triggered the build. - Target the email directly to the GitLab user's email address—you can even pull this from GitLab webhook payloads to automate notifications per committer.
- Use the built-in
Forward status to GitLab and use GitLab's notifications
Configure your Azure DevOps pipeline to update the GitLab commit status when builds/releases pass or fail. Then, have your GitLab users enable email notifications for failed pipeline statuses in their GitLab settings. While this won't include the full Azure DevOps error log directly in the email, it will alert them to the failure and link back to the Azure DevOps build for deep dives. This works well if your team already relies on GitLab's notification workflows.
A quick note on licenses: Adding external users as guests to your Azure DevOps project would let them receive native notifications, but this would consume your free user slots (or require additional licenses if you exceed 5)—which you said you don't want to do. So the custom pipeline email method is the best fit for your setup.
内容的提问来源于stack exchange，提问作者Peter Wyss
