diff options
author | 2017-03-10 14:45:09 +0000 | |
---|---|---|
committer | 2017-03-10 17:40:34 +0000 | |
commit | e41014a72d7cf3a1fb4c24110d2db9163bc66d15 (patch) | |
tree | 4bc853f0659938513c6dfef53cbb526c149f9c89 | |
parent | 36958806f2cd38dc51e64cd7bcc557bd143bbdb6 (diff) |
Adding an opaque Platform message with keys and values. As a first step
towards cross-platform support, we will add a hack that takes some values via
a command line flag, and pass them on to a remote execution engine (next CL).
TESTED=no change
RELNOTES: n/a
--
PiperOrigin-RevId: 149753326
MOS_MIGRATED_REVID=149753326
-rw-r--r-- | src/main/protobuf/remote_protocol.proto | 12 |
1 files changed, 7 insertions, 5 deletions
diff --git a/src/main/protobuf/remote_protocol.proto b/src/main/protobuf/remote_protocol.proto index c094febe45..e8f60cc3f5 100644 --- a/src/main/protobuf/remote_protocol.proto +++ b/src/main/protobuf/remote_protocol.proto @@ -32,12 +32,14 @@ message FileMetadata { bool executable = 3; } +// A Platform is defined by a set of opaque name-value pairs. message Platform { - // The contents of this message will be determined later, with the purpose of - // specifying everything that is required for the action execution, but cannot - // be uploaded as part of the inputs. - // It will likely contain fields as architecture, vendor, OS + version, - // ABI, etc. + message Property { + string name = 1; + string value = 2; + } + // Entries are sorted by name,value to ensure a canonical form. + repeated Property entry = 1; } // All the fields of this message have the following in common: they are |