1// Copyright 2022 The ChromiumOS Authors 2// Use of this source code is governed by a BSD-style license that can be 3// found in the LICENSE file. 4 5syntax = "proto3"; 6 7package chromiumos.test.api; 8 9option go_package = "go.chromium.org/chromiumos/config/go/test/api"; 10 11import "chromiumos/storage_path.proto"; 12 13// Defines the properties needed for archiving XTS suite results to be ingested 14// by the XTS pipeline for release qualification and monitoring. 15// NEXT TAG: 7 16message XtsArchiverMetadata { 17 // Whether the run is for AL project. 18 bool al_run = 1; 19 20 // The full product/device information. 21 // For ChromeOS the format is: 22 // <board_name>.<model_name>-<board_variant> 23 // e.g.: brya.brya-arcnext 24 string product = 2; 25 26 // A full build name. 27 // For ChromeOS the format is: 28 // <board_name>_<board_variant>-<channel>/<build_version> 29 // e.g. hatch-release/R108-15183.0.0 30 // 31 // For AL the format is: 32 // <build_target>/<build_id> 33 // e.g. brya-trunk_staging-userdebug/brya-ota-12644700 34 string build = 3; 35 36 // ID of the parent swarming task for the build. Can be empty if job 37 // is not scheduled through swarming. 38 string parent_swarming_task_id = 4; 39 40 // The GCS path prefix to upload XTS result file to be ingested by 41 // the XTS pipeline. 42 string results_gcs_prefix = 5; 43 44 // The GCS path prefix to upload XTS result file for APFE approval. 45 string apfe_gcs_prefix = 6; 46} 47 48// NEXT TAG: 5 49message PublishGcsMetadata { 50 // GCS location where artifacts will be uploaded. 51 StoragePath gcs_path = 1; 52 // Local file path to GCS creds that should be used for GCS upload. 53 StoragePath service_account_creds_file_path = 2; 54 55 // Metadata for the XTS archiving process. 56 XtsArchiverMetadata xts_archiver_metadata = 3; 57 58 // Whether to include the step to archive XTS results. 59 bool enable_xts_archiver = 4; 60}