CruiseControl.NET:使用 SVN 用户名发送电子邮件到 ActiveDirectory 映射
是否可以将 CruiseControl.NET 配置为向对损坏的版本进行修改的用户发送电子邮件通过将其 SVN 用户名映射到相应的 Active-Directory 别名(从而检索正确的、更新的电子邮件地址)。
我们的 SVN 服务器设置为允许某个 Active-Directory 组的用户读取和提交更改:我不想每次将用户添加到 Active-Directory 中的程序员组时都必须维护 CruiseControl.NET 配置。目录。
多谢!
Is it possible to configure CruiseControl.NET to send an email to the user(s) that did modifications to a broken build by mapping their SVN username to the corresponding Active-Directory alias (hence retrieving the correct, updated email address).
Our SVN server is set-up to allow users of a certain Active-Directory group to read and commit changes: I don't want to have to maintain the CruiseControl.NET config every time a user gets added to our Programmers group in Active-Directory.
Thanks a lot!
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
您想问如何确定最新提交者的电子邮件地址?假设您的用户的 subversion 用户名与其(非域限定的)AD 用户名相同,这非常简单。由于您正在使用 AD 向 svn 进行身份验证,所以我猜您已经拥有了这个。
要向提交者发送电子邮件以响应 cc.net 事件,请使用“modifierNotificationTypes”配置块(在“email”块中)定义何时应向他们发送电子邮件,并使用“converters”块告诉 cc.net 如何转换svn 用户名转换为电子邮件地址。这应该像添加“@yourcompany.com”一样简单,可以使用“regexConverter”来完成。以下是向提交者发送有关失败构建和第一个修复构建的电子邮件的示例:
查看 有关电子邮件发布者的 cc.net 文档,了解有关如何配置电子邮件阻止的更多详细信息。
Are you asking how to determine the email address of the latest committer? This is farily simple assuming that your user's subversion user names are the same as their (non-domain-qualified) AD user names. Since you're authenticating to svn using AD, I'm guessing you have this already.
To email committers in response to cc.net events, use the "modifierNotificationTypes" configuration block (in the "email" block) to define when they should be emailed, and use the "converters" block to tell cc.net how to convert the svn user name into an email address. This should be as simple as tacking on "@yourcompany.com", which can be accomplished with a "regexConverter". Here's an example that emails committers on failed builds and the first fixed build:
Check out the cc.net documentation on the email publisher for more details on how the email block can be configured.