基于线路的 SCM 责备信息存储在哪里? [英] Where is line based SCM blame information stored?

查看:69
本文介绍了基于线路的 SCM 责备信息存储在哪里?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我可以在 UI 中看到基于行的 SCM 责备信息,但它存储在哪里以及如何通过 Web API 检索?

I can see line based SCM blame information in UI, but where is it stored and how can I retrieve through web API?

我正在使用 Perforce 插件.

I am using Perforce plugin.

问题是 Perforce 插件从历史记录中找到了过错信息,因此如果用户在过去的分支中创建了债务,它仍然会在当前分支分析中显示在他的名字上.

The issue is that the Perforce plugin finds the blame information from history, and because of that if a user has created a debt in a past branch, it still shows on his name in the current branch analysis.

Perforce 插件没有任何这样的方法来禁止查看当前分支之外的历史记录.

The Perforce plugin does not have any such way to disable looking into history beyond the current branch.

我需要另辟蹊径,看看这个分行是否真的引入了债务.

I need to find another way to find out, if the debt is really introduced in this branch or not.

推荐答案

这里真正的问题是如何找到这个:

The real question here is how to find out this:

我需要另辟蹊径,看看这个分行是否真的引入了债务.

I need to find another way to find out, if the debt is really introduced in this branch or not.

正确的做法与过滤过错信息和/或禁止查看当前分支之外的历史无关.

The right way to do this has nothing to do with filtering out blame information and/or disable looking into history beyond the current branch.

解决该用例的正确方法(该分支中是否真的引入了债务)是设置 泄漏周期 到分支的起源".SonarQube 项目空间 将不断为您提供与该项目相比的项目状态基线(即新错误新债务新代码覆盖率等.请参阅泄漏期黄色窗格对).

The right approach to solve that use-case (is debt really introduced in this branch or not) is to set the Leak Period to the 'origin' of the branch. The SonarQube Project Space will then constantly give you the status of your project compared to that baseline (i.e. New Bugs, New Debt, Coverage on New Code etc. see Leak Period yellow pane on the right).

这篇关于基于线路的 SCM 责备信息存储在哪里?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆