aboutsummaryrefslogtreecommitdiffstats
path: root/sonar-scanner-protocol
diff options
context:
space:
mode:
authorJulien HENRY <julien.henry@sonarsource.com>2017-07-19 17:27:29 +0200
committerJulien HENRY <julien.henry@sonarsource.com>2017-08-07 11:44:06 +0200
commit882a48ee26c694880eabdacaa4a0bfc031a9990d (patch)
tree06932647240587d91f2fefcb12e61d73621785b1 /sonar-scanner-protocol
parent9ad1582eadfd88239c359bd4cad50d589f65c2a3 (diff)
downloadsonarqube-882a48ee26c694880eabdacaa4a0bfc031a9990d.tar.gz
sonarqube-882a48ee26c694880eabdacaa4a0bfc031a9990d.zip
SONAR-9576 Add incremental mode flag and file status in scanner report
Diffstat (limited to 'sonar-scanner-protocol')
-rw-r--r--sonar-scanner-protocol/src/main/protobuf/scanner_report.proto12
1 files changed, 11 insertions, 1 deletions
diff --git a/sonar-scanner-protocol/src/main/protobuf/scanner_report.proto b/sonar-scanner-protocol/src/main/protobuf/scanner_report.proto
index 7033c31ce75..75a93b65e12 100644
--- a/sonar-scanner-protocol/src/main/protobuf/scanner_report.proto
+++ b/sonar-scanner-protocol/src/main/protobuf/scanner_report.proto
@@ -30,13 +30,14 @@ option optimize_for = SPEED;
message Metadata {
int64 analysis_date = 1;
- // TODO should we keep this project_key here or not ? Because it's a duplication of Component.key
string organization_key = 2;
+ // TODO should we keep this project_key here or not ? Because it's a duplication of Component.key
string project_key = 3;
string branch = 4;
int32 root_component_ref = 5;
bool cross_project_duplication_activated = 6;
map<string, QProfile> qprofiles_per_language = 7;
+ bool incremental = 8;
message QProfile {
string key = 1;
@@ -91,6 +92,7 @@ message Component {
int32 lines = 11;
// Only available on PROJECT and MODULE types
string description = 12;
+ FileStatus status = 13;
enum ComponentType {
UNSET = 0;
@@ -100,6 +102,14 @@ message Component {
FILE = 4;
}
+ // For incremental mode
+ enum FileStatus {
+ UNAVAILABLE = 0;
+ SAME = 1;
+ CHANGED = 2;
+ ADDED = 3;
+ }
+
}
message Measure {