我们如何使SonarLint在Eclipse中的启动速度更快，有很多项目？ [英] How can we make SonarLint startup faster in Eclipse with lots of projects?

问题描述

在我们的案例中，我们有一个父项目（trunk），其中所有插件都有子项目，我们希望所有子项目具有相同的规则。为了使维护变得更简单，我们认为我们可以将eclipse中的所有插件项目绑定到trunk（因此我们只需要批量更新它们）。
这里的问题是，由于某种原因，它总是加载每个项目的所有子项目。 1）它们总是相同的2）在子项目的调用中没有更多的信息，前一个呼叫没有得到。

如果我们绑定每个项目到SonarLint的真正正确的项目，这是很大的努力。 （我们有数百个插件。）
仍然，对于我们在Eclipse中的100+插件项目，SonarLint需要几分钟时间才能从服务器获取所有信息。

我们如何使SonarLint更快？有推荐的方法吗？我们可以帮助改善这种情况的逻辑吗？

解决方案

我认为你的问题的标题是令人困惑的。这不是关于SonarLint启动，而是关于SonarLint更新所有绑定功能。

我已经创建了一个我们将在下一个版本中修复的故障单：
https://jira.sonarsource.com/browse/SLE-200

请注意，没有将Eclipse项目绑定到正确的SonarQube项目/模块将阻止本地和远程问题之间的正确匹配。这意味着在SonarQube方面被标记为不会修复或假阳性的问题不会在Eclipse中被静音。

你说过映射很多项目是乏味的。自动绑定功能如何？如果无法正确猜测本地和远程项目之间的绑定，我建议您在 SonarLint Google group ，以便我们可以调查原因。

In our case we had a parent project (trunk) where all plug-ins where sub-projects and we want all the sub projects to have the same rules. In order to make maintenance easier we thought we could bind all plug-in projects in eclipse to trunk (so we can just batch update them etc.). The problem here is that for some reason it always loads all sub projects for each project. 1) they are always the same 2) there is not more information in the call of the sub-project that the former call did not get.

If we bind each project to the real correct project in SonarLint that is a lot of effort. (we have hundreds of plug-ins.) Still, for our 100+ plug-in projects that we have in Eclipse SonarLint takes some minutes to get all the info from the server.

How can we make SonarLint faster? Is there a recommended way? Can we help to improve the logic for this scenario?

解决方案

I think the title of your question is confusing. This is not about SonarLint startup, but about SonarLint "update all bindings" feature.

I have created a ticket that we will try to fix in the next version: https://jira.sonarsource.com/browse/SLE-200

Note that not binding Eclipse project to the correct SonarQube project/module will prevent correct match between local and remote issues. It means issues flagged as "won't fix" or "false positive" on SonarQube side will not be muted in Eclipse.

You said mapping many projects is tedious. What about the auto-bind feature? If it is failing to correctly guess binding between local and remote projects, I encourage you to open a thread on the SonarLint Google group to so that we can investigate the reason.

这篇关于我们如何使SonarLint在Eclipse中的启动速度更快，有很多项目？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！