From 444e029a905bda6baabb19ab5ff8cef50af23f37 Mon Sep 17 00:00:00 2001 From: =?utf8?q?S=C3=A9bastien=20Lesaint?= Date: Mon, 9 Jan 2017 13:57:09 +0100 Subject: [PATCH] SONAR-8593 add organization key to analysis report --- .../src/main/protobuf/scanner_report.proto | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/sonar-scanner-protocol/src/main/protobuf/scanner_report.proto b/sonar-scanner-protocol/src/main/protobuf/scanner_report.proto index 5b5d5b59b50..01a9cc7ead8 100644 --- a/sonar-scanner-protocol/src/main/protobuf/scanner_report.proto +++ b/sonar-scanner-protocol/src/main/protobuf/scanner_report.proto @@ -31,11 +31,12 @@ 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 project_key = 2; - string branch = 3; - int32 root_component_ref = 4; - bool cross_project_duplication_activated = 5; - map qprofiles_per_language = 6; + string organization_key = 2; + string project_key = 3; + string branch = 4; + int32 root_component_ref = 5; + bool cross_project_duplication_activated = 6; + map qprofiles_per_language = 7; message QProfile { string key = 1; -- 2.39.5