Sonarqube 5.1核心自动分配功能不起作用 [英] Sonarqube 5.1 core auto assign feature not working

问题描述

我听说sonarqube 5.1自内置以来就不需要问题分配插件.但是，每当我通过SVN提交并通过jenkins运行声纳时，所有团队都会收到一封电子邮件，指出存在问题，但未分配问题给最后一个提交者或任何人.

I've heard that issue assign plugin is not needed in sonarqube 5.1 since its built in. But whenever I committed through SVN and run sonar through jenkins all of the team gets an email saying there is an issue but issues are not assigned to the last committer or to anybody.

但是，当我通过声纳查看代码时，我可以看到它在其前面显示了承诺人员的姓名.因此，我认为问题不在于SVN连接或用户名标识. (我们使用相同的用户名登录SVN和sonarqube)

But when I view the code through sonar I can see it displays the committed persons name in-front of it. Therefore I think that the issue is not with SVN connection or user name identificaiton. (We use same usernames to log in to both SVN and sonarqube)

我已经使用了所有给定的配置以及不同配置的组合.对于栈溢出来说，这可能不是一个有效的问题，但是我非常感谢您提供任何可能的帮助.

I've used all the given configurations and the combinations of different configurations. This may not be a valid issue for stack overflow but I would really appreciate any possible help to move forward.

以下是我已在sonarqube中安装的插件.我刚刚删除了SCM Stats插件

Following are the plugins that i have installed in sonarqube. I just removed SCM Stats plugin

谢谢.

推荐答案

我已按照注释中给出的说明解决了该问题.

I solved the issue with the directions given in the comments.

通过获取SCM作者名称(在Sonarqube代码视图的左侧)，并将确切名称添加为SCM帐户.

By getting the SCM author name (On the left side of Sonarqube code view) and add the exact name as a SCM account.

Settings -> Security -> Users -> Edit -> Add SCM account

这篇关于Sonarqube 5.1核心自动分配功能不起作用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！