Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(112)

Side by Side Diff: discovery/googleapis_beta/toolresults__v1beta3.json

Issue 2226653002: Api-roll 40: 2016-08-08 (Closed) Base URL: git@github.com:dart-lang/googleapis.git@master
Patch Set: Created 4 years, 4 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
1 { 1 {
2 "auth": { 2 "auth": {
3 "oauth2": { 3 "oauth2": {
4 "scopes": { 4 "scopes": {
5 "https://www.googleapis.com/auth/cloud-platform": { 5 "https://www.googleapis.com/auth/cloud-platform": {
6 "description": "View and manage your data across Google Clou d Platform services" 6 "description": "View and manage your data across Google Clou d Platform services"
7 } 7 }
8 } 8 }
9 } 9 }
10 }, 10 },
11 "basePath": "/toolresults/v1beta3/projects/", 11 "basePath": "/toolresults/v1beta3/projects/",
12 "baseUrl": "https://www.googleapis.com/toolresults/v1beta3/projects/", 12 "baseUrl": "https://www.googleapis.com/toolresults/v1beta3/projects/",
13 "batchPath": "batch", 13 "batchPath": "batch",
14 "canonicalName": "Tool Results", 14 "canonicalName": "Tool Results",
15 "description": "Reads and publishes results from Cloud Test Lab.", 15 "description": "Reads and publishes results from Cloud Test Lab.",
16 "discoveryVersion": "v1", 16 "discoveryVersion": "v1",
17 "documentationLink": "https://developers.google.com/cloud-test-lab/", 17 "documentationLink": "https://developers.google.com/cloud-test-lab/",
18 "etag": "\"C5oy1hgQsABtYOYIOXWcR3BgYqU/24RiHeeznw3XkPH7TIR188r4N0M\"", 18 "etag": "\"C5oy1hgQsABtYOYIOXWcR3BgYqU/dcuwhJF8v2eGhAkOhN_qdalBHBw\"",
19 "icons": { 19 "icons": {
20 "x16": "http://www.google.com/images/icons/product/search-16.gif", 20 "x16": "http://www.google.com/images/icons/product/search-16.gif",
21 "x32": "http://www.google.com/images/icons/product/search-32.gif" 21 "x32": "http://www.google.com/images/icons/product/search-32.gif"
22 }, 22 },
23 "id": "toolresults:v1beta3", 23 "id": "toolresults:v1beta3",
24 "kind": "discovery#restDescription", 24 "kind": "discovery#restDescription",
25 "name": "toolresults", 25 "name": "toolresults",
26 "ownerDomain": "google.com", 26 "ownerDomain": "google.com",
27 "ownerName": "Google", 27 "ownerName": "Google",
28 "parameters": { 28 "parameters": {
(...skipping 663 matching lines...) Expand 10 before | Expand all | Expand 10 after
692 } 692 }
693 } 693 }
694 } 694 }
695 } 695 }
696 } 696 }
697 } 697 }
698 } 698 }
699 } 699 }
700 } 700 }
701 }, 701 },
702 "revision": "20160715", 702 "revision": "20160805",
703 "rootUrl": "https://www.googleapis.com/", 703 "rootUrl": "https://www.googleapis.com/",
704 "schemas": { 704 "schemas": {
705 "Any": { 705 "Any": {
706 "description": "`Any` contains an arbitrary serialized protocol buff er message along with a URL that describes the type of the serialized message.\n \nProtobuf library provides support to pack/unpack Any values in the form of uti lity functions or additional generated methods of the Any type.\n\nExample 1: Pa ck and unpack a message in C++.\n\nFoo foo = ...; Any any; any.PackFrom(foo); .. . if (any.UnpackTo(&foo)) { ... }\n\nExample 2: Pack and unpack a message in Jav a.\n\nFoo foo = ...; Any any = Any.pack(foo); ... if (any.is(Foo.class)) { foo = any.unpack(Foo.class); }\n\nExample 3: Pack and unpack a message in Python.\n\n foo = Foo(...) any = Any() any.Pack(foo) ... if any.Is(Foo.DESCRIPTOR): any.Unpa ck(foo) ...\n\nThe pack methods provided by protobuf library will by default use 'type.googleapis.com/full.type.name' as the type URL and the unpack methods onl y use the fully qualified type name after the last '/' in the type URL, for exam ple \"foo.bar.com/x/y.z\" will yield type name \"y.z\".\n\n\n\nJSON ==== The JSO N representation of an `Any` value uses the regular representation of the deseri alized, embedded message, with an additional field `@type` which contains the ty pe URL. Example:\n\npackage google.profile; message Person { string first_name = 1; string last_name = 2; }\n\n{ \"@type\": \"type.googleapis.com/google.profile .Person\", \"firstName\": , \"lastName\": }\n\nIf the embedded message type is well-known and has a custom JSON representation, that representation will be emb edded adding a field `value` which holds the custom JSON in addition to the `@ty pe` field. Example (for message [google.protobuf.Duration][]):\n\n{ \"@type\": \ "type.googleapis.com/google.protobuf.Duration\", \"value\": \"1.212s\" }", 706 "description": "`Any` contains an arbitrary serialized protocol buff er message along with a URL that describes the type of the serialized message.\n \nProtobuf library provides support to pack/unpack Any values in the form of uti lity functions or additional generated methods of the Any type.\n\nExample 1: Pa ck and unpack a message in C++.\n\nFoo foo = ...; Any any; any.PackFrom(foo); .. . if (any.UnpackTo(&foo)) { ... }\n\nExample 2: Pack and unpack a message in Jav a.\n\nFoo foo = ...; Any any = Any.pack(foo); ... if (any.is(Foo.class)) { foo = any.unpack(Foo.class); }\n\nExample 3: Pack and unpack a message in Python.\n\n foo = Foo(...) any = Any() any.Pack(foo) ... if any.Is(Foo.DESCRIPTOR): any.Unpa ck(foo) ...\n\nThe pack methods provided by protobuf library will by default use 'type.googleapis.com/full.type.name' as the type URL and the unpack methods onl y use the fully qualified type name after the last '/' in the type URL, for exam ple \"foo.bar.com/x/y.z\" will yield type name \"y.z\".\n\n\n\nJSON ==== The JSO N representation of an `Any` value uses the regular representation of the deseri alized, embedded message, with an additional field `@type` which contains the ty pe URL. Example:\n\npackage google.profile; message Person { string first_name = 1; string last_name = 2; }\n\n{ \"@type\": \"type.googleapis.com/google.profile .Person\", \"firstName\": , \"lastName\": }\n\nIf the embedded message type is well-known and has a custom JSON representation, that representation will be emb edded adding a field `value` which holds the custom JSON in addition to the `@ty pe` field. Example (for message [google.protobuf.Duration][]):\n\n{ \"@type\": \ "type.googleapis.com/google.protobuf.Duration\", \"value\": \"1.212s\" }",
707 "id": "Any", 707 "id": "Any",
708 "properties": { 708 "properties": {
709 "typeUrl": { 709 "typeUrl": {
710 "description": "A URL/resource name whose content describes the type of the serialized protocol buffer message.\n\nFor URLs which use the sc heme `http`, `https`, or no scheme, the following restrictions and interpretatio ns apply:\n\n* If no scheme is provided, `https` is assumed. * The last segment of the URL's path must represent the fully qualified name of the type (as in `pa th/google.protobuf.Duration`). The name should be in a canonical form (e.g., lea ding \".\" is not accepted). * An HTTP GET on the URL must yield a [google.proto buf.Type][] value in binary format, or produce an error. * Applications are allo wed to cache lookup results based on the URL, or have them precompiled into a bi nary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)\n\nS chemes other than `http`, `https` (or the empty scheme) might be used with imple mentation specific semantics.", 710 "description": "A URL/resource name whose content describes the type of the serialized protocol buffer message.\n\nFor URLs which use the sc heme `http`, `https`, or no scheme, the following restrictions and interpretatio ns apply:\n\n* If no scheme is provided, `https` is assumed. * The last segment of the URL's path must represent the fully qualified name of the type (as in `pa th/google.protobuf.Duration`). The name should be in a canonical form (e.g., lea ding \".\" is not accepted). * An HTTP GET on the URL must yield a [google.proto buf.Type][] value in binary format, or produce an error. * Applications are allo wed to cache lookup results based on the URL, or have them precompiled into a bi nary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)\n\nS chemes other than `http`, `https` (or the empty scheme) might be used with imple mentation specific semantics.",
711 "type": "string" 711 "type": "string"
712 }, 712 },
713 "value": { 713 "value": {
714 "description": "Must be a valid serialized protocol buffer o f the above specified type.", 714 "description": "Must be a valid serialized protocol buffer o f the above specified type.",
715 "format": "byte", 715 "format": "byte",
716 "type": "string" 716 "type": "string"
717 } 717 }
718 }, 718 },
719 "type": "object" 719 "type": "object"
720 }, 720 },
721 "Duration": { 721 "Duration": {
722 "description": "A Duration represents a signed, fixed-length span of time represented as a count of seconds and fractions of seconds at nanosecond r esolution. It is independent of any calendar and concepts like \"day\" or \"mont h\". It is related to Timestamp in that the difference between two Timestamp val ues is a Duration and it can be added or subtracted from a Timestamp. Range is a pproximately +-10,000 years.\n\nExample 1: Compute Duration from two Timestamps in pseudo code.\n\nTimestamp start = ...; Timestamp end = ...; Duration duration = ...;\n\nduration.seconds = end.seconds - start.seconds; duration.nanos = end. nanos - start.nanos;\n\nif (duration.seconds 0) { duration.seconds += 1; durati on.nanos -= 1000000000; } else if (durations.seconds > 0 && duration.nanos < 0) { duration.seconds -= 1; duration.nanos += 1000000000; }\n\nExample 2: Compute T imestamp from Timestamp + Duration in pseudo code.\n\nTimestamp start = ...; Dur ation duration = ...; Timestamp end = ...;\n\nend.seconds = start.seconds + dura tion.seconds; end.nanos = start.nanos + duration.nanos;\n\nif (end.nanos = 10000 00000) { end.seconds += 1; end.nanos -= 1000000000; }", 722 "description": "A Duration represents a signed, fixed-length span of time represented as a count of seconds and fractions of seconds at nanosecond r esolution. It is independent of any calendar and concepts like \"day\" or \"mont h\". It is related to Timestamp in that the difference between two Timestamp val ues is a Duration and it can be added or subtracted from a Timestamp. Range is a pproximately +-10,000 years.\n\nExample 1: Compute Duration from two Timestamps in pseudo code.\n\nTimestamp start = ...; Timestamp end = ...; Duration duration = ...;\n\nduration.seconds = end.seconds - start.seconds; duration.nanos = end. nanos - start.nanos;\n\nif (duration.seconds 0) { duration.seconds += 1; durati on.nanos -= 1000000000; } else if (durations.seconds > 0 && duration.nanos < 0) { duration.seconds -= 1; duration.nanos += 1000000000; }\n\nExample 2: Compute T imestamp from Timestamp + Duration in pseudo code.\n\nTimestamp start = ...; Dur ation duration = ...; Timestamp end = ...;\n\nend.seconds = start.seconds + dura tion.seconds; end.nanos = start.nanos + duration.nanos;\n\nif (end.nanos = 10000 00000) { end.seconds += 1; end.nanos -= 1000000000; }\n\nExample 3: Compute Dura tion from datetime.timedelta in Python.\n\ntd = datetime.timedelta(days=3, minut es=10) duration = Duration() duration.FromTimedelta(td)",
723 "id": "Duration", 723 "id": "Duration",
724 "properties": { 724 "properties": {
725 "nanos": { 725 "nanos": {
726 "description": "Signed fractions of a second at nanosecond r esolution of the span of time. Durations less than one second are represented wi th a 0 `seconds` field and a positive or negative `nanos` field. For durations o f one second or more, a non-zero value for the `nanos` field must be of the same sign as the `seconds` field. Must be from -999,999,999 to +999,999,999 inclusiv e.", 726 "description": "Signed fractions of a second at nanosecond r esolution of the span of time. Durations less than one second are represented wi th a 0 `seconds` field and a positive or negative `nanos` field. For durations o f one second or more, a non-zero value for the `nanos` field must be of the same sign as the `seconds` field. Must be from -999,999,999 to +999,999,999 inclusiv e.",
727 "format": "int32", 727 "format": "int32",
728 "type": "integer" 728 "type": "integer"
729 }, 729 },
730 "seconds": { 730 "seconds": {
731 "description": "Signed seconds of the span of time. Must be from -315,576,000,000 to +315,576,000,000 inclusive.", 731 "description": "Signed seconds of the span of time. Must be from -315,576,000,000 to +315,576,000,000 inclusive.",
732 "format": "int64", 732 "format": "int64",
(...skipping 575 matching lines...) Expand 10 before | Expand all | Expand 10 after
1308 }, 1308 },
1309 "widthPx": { 1309 "widthPx": {
1310 "description": "The width of the thumbnail, in pixels.\n\nAl ways set.", 1310 "description": "The width of the thumbnail, in pixels.\n\nAl ways set.",
1311 "format": "int32", 1311 "format": "int32",
1312 "type": "integer" 1312 "type": "integer"
1313 } 1313 }
1314 }, 1314 },
1315 "type": "object" 1315 "type": "object"
1316 }, 1316 },
1317 "Timestamp": { 1317 "Timestamp": {
1318 "description": "A Timestamp represents a point in time independent o f any time zone or calendar, represented as seconds and fractions of seconds at nanosecond resolution in UTC Epoch time. It is encoded using the Proleptic Grego rian Calendar which extends the Gregorian calendar backwards to year one. It is encoded assuming all minutes are 60 seconds long, i.e. leap seconds are \"smeare d\" so that no leap second table is needed for interpretation. Range is from 000 1-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that rang e, we ensure that we can convert to and from RFC 3339 date strings. See [https:/ /www.ietf.org/rfc/rfc3339.txt](https://www.ietf.org/rfc/rfc3339.txt).\n\nExample 1: Compute Timestamp from POSIX `time()`.\n\nTimestamp timestamp; timestamp.set _seconds(time(NULL)); timestamp.set_nanos(0);\n\nExample 2: Compute Timestamp fr om POSIX `gettimeofday()`.\n\nstruct timeval tv; gettimeofday(&tv, NULL);\n\nTim estamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_us ec * 1000);\n\nExample 3: Compute Timestamp from Win32 `GetSystemTimeAsFileTime( )`.\n\nFILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dw HighDateTime) << 32) | ft.dwLowDateTime;\n\n// A Windows tick is 100 nanoseconds . Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((tick s / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100));\n\nExample 4: Compute Timestamp from Java `System.currentTimeMillis()` .\n\nlong millis = System.currentTimeMillis();\n\nTimestamp timestamp = Timestam p.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000 000)).build();\n\n\n\nExample 5: Compute Timestamp from current time in Python.\ n\nnow = time.time() seconds = int(now) nanos = int((now - seconds) * 10**9) tim estamp = Timestamp(seconds=seconds, nanos=nanos)", 1318 "description": "A Timestamp represents a point in time independent o f any time zone or calendar, represented as seconds and fractions of seconds at nanosecond resolution in UTC Epoch time. It is encoded using the Proleptic Grego rian Calendar which extends the Gregorian calendar backwards to year one. It is encoded assuming all minutes are 60 seconds long, i.e. leap seconds are \"smeare d\" so that no leap second table is needed for interpretation. Range is from 000 1-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that rang e, we ensure that we can convert to and from RFC 3339 date strings. See [https:/ /www.ietf.org/rfc/rfc3339.txt](https://www.ietf.org/rfc/rfc3339.txt).\n\nExample 1: Compute Timestamp from POSIX `time()`.\n\nTimestamp timestamp; timestamp.set _seconds(time(NULL)); timestamp.set_nanos(0);\n\nExample 2: Compute Timestamp fr om POSIX `gettimeofday()`.\n\nstruct timeval tv; gettimeofday(&tv, NULL);\n\nTim estamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_us ec * 1000);\n\nExample 3: Compute Timestamp from Win32 `GetSystemTimeAsFileTime( )`.\n\nFILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dw HighDateTime) << 32) | ft.dwLowDateTime;\n\n// A Windows tick is 100 nanoseconds . Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((tick s / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100));\n\nExample 4: Compute Timestamp from Java `System.currentTimeMillis()` .\n\nlong millis = System.currentTimeMillis();\n\nTimestamp timestamp = Timestam p.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000 000)).build();\n\n\n\nExample 5: Compute Timestamp from current time in Python.\ n\ntimestamp = Timestamp() timestamp.GetCurrentTime()",
1319 "id": "Timestamp", 1319 "id": "Timestamp",
1320 "properties": { 1320 "properties": {
1321 "nanos": { 1321 "nanos": {
1322 "description": "Non-negative fractions of a second at nanose cond resolution. Negative second values with fractions must still have non-negat ive nanos values that count forward in time. Must be from 0 to 999,999,999 inclu sive.", 1322 "description": "Non-negative fractions of a second at nanose cond resolution. Negative second values with fractions must still have non-negat ive nanos values that count forward in time. Must be from 0 to 999,999,999 inclu sive.",
1323 "format": "int32", 1323 "format": "int32",
1324 "type": "integer" 1324 "type": "integer"
1325 }, 1325 },
1326 "seconds": { 1326 "seconds": {
1327 "description": "Represents seconds of UTC time since Unix ep och 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to 9999-12-31T23:59: 59Z inclusive.", 1327 "description": "Represents seconds of UTC time since Unix ep och 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to 9999-12-31T23:59: 59Z inclusive.",
1328 "format": "int64", 1328 "format": "int64",
(...skipping 74 matching lines...) Expand 10 before | Expand all | Expand 10 after
1403 "description": "The test case to which this output file belo ngs.\n\n- In response: present if set by create/update request - In create/updat e request: optional" 1403 "description": "The test case to which this output file belo ngs.\n\n- In response: present if set by create/update request - In create/updat e request: optional"
1404 } 1404 }
1405 }, 1405 },
1406 "type": "object" 1406 "type": "object"
1407 } 1407 }
1408 }, 1408 },
1409 "servicePath": "toolresults/v1beta3/projects/", 1409 "servicePath": "toolresults/v1beta3/projects/",
1410 "title": "Cloud Tool Results API", 1410 "title": "Cloud Tool Results API",
1411 "version": "v1beta3" 1411 "version": "v1beta3"
1412 } 1412 }
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698