Sonar 5.1.X仍然可以进行连续检查吗? [英] Does continuous inspection still work with Sonar 5.1.X?

问题描述

我正在尝试使用SonarQube 5.1.1对我们的(Java)项目进行预览分析.我可以生成本地报告，但是没有覆盖数据，也收到消息[INFO] [XX:YY:ZZ.ZZZ] Build Breaker plugin is no more supported in preview/incremental mode.

I'm trying to run a preview analysis for a (Java) project of ours with SonarQube 5.1.1. I am able to get a local report generated, however I get no coverage data, and I also get the message [INFO] [XX:YY:ZZ.ZZZ] Build Breaker plugin is no more supported in preview/incremental mode.

如果我在此处进行了检查，则页面显示Starting with SonarQube 5.1, the Build Breaker plugin does not work any longer in the preview & incremental modes.

If I check here, the page says that Starting with SonarQube 5.1, the Build Breaker plugin does not work any longer in the preview & incremental modes..

我很困惑-我认为为了持续检查，需要构建破坏者插件.不再是这样吗? SonarQube中的概念是否发生了变化?

I'm confused - I thought that for continuous inspection one needs the build breaker plugin. Is that no longer so? Has the concept in SonarQube changed?

为什么运行预览分析时没有得到覆盖率数据?

Why am I not getting coverage data when running a preview analysis?

推荐答案

我不知道您在哪里读过这篇文章，但是连续检查与预览/增量模式或构建破坏程序插件没有特别关系-它是甚至与SonarQube都没有关系(即使它已被SonarSource从推入一开始).

I don't know where you've read this, but continuous inspection is not specifically related to the preview/incremental mode nor to the build breaker plugin - it's not even related to SonarQube (even though it has been pushed by SonarSource from the very beginning).

以下是关键点:

• 连续检查是关于尽可能多地分析代码以监视(并最终提高)代码质量的方法.无论使用哪种工具.
• 在SonarQube上，这意味着运行分析将信息推送到服务器上，以便您可以监视正在发生的事情并针对应用程序组合采取必要的操作.

很显然，当您是一名开发人员时，您希望尽早管理这些问题，然后再将它们推送到源代码存储库中.但是经验告诉我们，阻止由于问题而导致的任何代码推送是一种错误的模式-因为某些问题可能是错误肯定的，或者在上下文中不相关(并且仍然是您想要的，并且有权推送您的代码).这就是为什么我们认为构建破坏者插件与所有这些不一致的原因，并且它将在即将发布的SQ版本中被与这些概念更匹配的本机功能取代:

Obviously, when you are a developer, you'd like to manage those issues early, before they even get pushed to the source code repository. But experience tells us that preventing any code push because of issues is a bad pattern - because some issues might be false-positive or not relevant in the context (and still you want - and have the right, to push your code). This is why we feel that the build breaker plugin is not aligned with all this, and it will be replaced in upcoming versions of SQ by native features that match better these concepts:

• 非常高效的代码分析，可以以光速显示IDE中的问题-但无需计算指标
• 预览模式将计算所有内容，并可以在将代码推送到源代码存储库之前检查质量门-不会影响服务器上的结果
  • 在这种情况下，使用日志中找到的一些特定信息，CI可能会导致构建失败
  • Very efficient code analysis to display issues in the IDE at the speed of light - but without computing metrics
  • Preview mode that will compute everything and make it possible to check quality gate before pushing code to the source code repository - without impacting the results on the server
    • and in this case, using some specific information found in the logs, it will be possible for a CI to fail a build

    这篇关于Sonar 5.1.X仍然可以进行连续检查吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！