TFS2010：禁用私人构建的电子邮件警报
我们正在招募新开发人员并鼓励他们使用 TFS2010 的私有版本 功能 - 构建是使用搁置集完成的，因此您可以看到更改会产生什么影响。
我们将 TFS 设置为向开发团队发送电子邮件，这就是导致问题的原因：TFS 通过电子邮件向整个团队发送私有构建的结果，这会在私有构建失败时导致对“公共”构建的当前状态产生混乱。
电子邮件中唯一的区别是私有构建不标记源，因此主题行是 Scrum Build 8518 failed 而不是 Scrum Build CI Build_20111007.5 success。虽然这足以在您习惯后区分这两者，但一开始会让人感到困惑。
是否可以禁用私人构建的电子邮件警报？或者，如果构建对于更明确的内容是私有的，是否可以更改主题行？
我查看了 JobStatusAgent 配置和电子邮件模板，但我看不到任何有帮助的内容。我们正在使用默认模板（如果相关的话）。
We are taking on new developers and encouraging them to use TFS2010's private builds feature - a build is done using a shelveset, so you can see what impact changes will have.
We have TFS set to email the dev team, and that's what's causing the problem: TFS emails the whole team with the result of the private build, which causes confusion over the current state of the 'public' build when a private build fails.
The only difference in the email is that private builds don't label the sources, so the subject line is Scrum Build 8518 failed rather than Scrum Build CI Build_20111007.5 succeeded. While this is enough to be able to distinguish the two once you're used to it, it's confusing at first.
Is it possible to disable the email alert for private builds? Alternatively, is it possible to change the subject line if the build is private to something more explicit?
I've looked at the JobStatusAgent config and the email templates, but I can't see anything there that will help. We are using the default template, if that's relevant.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
绝对推荐@Edward 建议的警报浏览器。您不需要整个团队来安装电动工具，只需几个团队成员来管理项目级别警报就足够了。
使用警报资源管理器，您可以设置警报以筛选
请求者或请求者字段。对于持续集成构建，Requested For字段包含其签入触发构建的用户。Requested By字段包含请求构建的用户。对于 CI 或计划构建，这将是构建代理服务帐户。不幸的是，如果您有手动请求的公共构建，这并没有真正的帮助。Definitely recommend the Alerts Explorer as suggested by @Edward. You don't need the whole team to install the Power Tools, just a couple of team members to manage Project level Alerts should suffice.
With the Alerts Explorer, you can then set up the alert to filter for the
Requested ByorRequested Forfields. In case of Continuous Integration builds, theRequested Forfield contains the user whose check-in triggered the build. TheRequested Byfield contains the user who requested the build. In case of CI or scheduled builds, this will be the Build Agent service account. Unfortunately, this doesn't really help if you have public builds that are manually requested.您是否使用Alerts Explorer 电动工具配置警报？它比开箱即用的警报功能强大得多。
您可以对警报进行更细粒度的配置 - 例如，标题包含“ CI ”、内部版本号字符串匹配或基于请求内部版本的人员。
Are you configuring your alerts with the Alerts Explorer power tool? It's much more powerful than the out-of-the-box alerts functionality.
You can configure more fine-grained configuration on the alerts - for example, Title contains " CI ", build number string matching, or based on the person requesting the builds.
请查看此处，我在其中描述了一种将名为“BuildType”的新构建参数插入到构建过程模板中的方法。
使用此附加参数，我们可以控制向 QA 团队发送（或不发送）电子邮件。
Please have a look here, where I 've discribe a method to insert a new build argument named "BuildType" into your Build Process Template.
Using this additional parameter we control the sending (or not) of an email to the QA-team.