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

Side by Side Diff: discovery/googleapis/cloudbuild__v1.json

Issue 2281923002: Api-roll 41: 2016-08-26 (Closed) Base URL: git@github.com:dart-lang/googleapis.git@master
Patch Set: Created 4 years, 3 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
« no previous file with comments | « discovery/googleapis/classroom__v1.json ('k') | discovery/googleapis/clouddebugger__v2.json » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
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 },
(...skipping 98 matching lines...) Expand 10 before | Expand all | Expand 10 after
109 "upload_protocol": { 109 "upload_protocol": {
110 "description": "Upload protocol for media (e.g. \"raw\", \"multipart \").", 110 "description": "Upload protocol for media (e.g. \"raw\", \"multipart \").",
111 "location": "query", 111 "location": "query",
112 "type": "string" 112 "type": "string"
113 } 113 }
114 }, 114 },
115 "protocol": "rest", 115 "protocol": "rest",
116 "resources": { 116 "resources": {
117 "projects": { 117 "projects": {
118 "resources": { 118 "resources": {
119 "triggers": {
120 "methods": {
121 "create": {
122 "description": "Creates a new BuildTrigger.\n\nThis API is experimental.",
123 "httpMethod": "POST",
124 "id": "cloudbuild.projects.triggers.create",
125 "parameterOrder": [
126 "projectId"
127 ],
128 "parameters": {
129 "projectId": {
130 "description": "ID of the project for which to configure automatic builds.",
131 "location": "path",
132 "required": true,
133 "type": "string"
134 }
135 },
136 "path": "v1/projects/{projectId}/triggers",
137 "request": {
138 "$ref": "BuildTrigger"
139 },
140 "response": {
141 "$ref": "BuildTrigger"
142 },
143 "scopes": [
144 "https://www.googleapis.com/auth/cloud-platform"
145 ]
146 },
147 "get": {
148 "description": "Gets information about a BuildTrigge r.\n\nThis API is experimental.",
149 "httpMethod": "GET",
150 "id": "cloudbuild.projects.triggers.get",
151 "parameterOrder": [
152 "projectId",
153 "triggerId"
154 ],
155 "parameters": {
156 "projectId": {
157 "description": "ID of the project that owns the trigger.",
158 "location": "path",
159 "required": true,
160 "type": "string"
161 },
162 "triggerId": {
163 "description": "ID of the BuildTrigger to ge t.",
164 "location": "path",
165 "required": true,
166 "type": "string"
167 }
168 },
169 "path": "v1/projects/{projectId}/triggers/{triggerId }",
170 "response": {
171 "$ref": "BuildTrigger"
172 },
173 "scopes": [
174 "https://www.googleapis.com/auth/cloud-platform"
175 ]
176 },
177 "list": {
178 "description": "Lists existing BuildTrigger.\n\nThis API is experimental.",
179 "httpMethod": "GET",
180 "id": "cloudbuild.projects.triggers.list",
181 "parameterOrder": [
182 "projectId"
183 ],
184 "parameters": {
185 "projectId": {
186 "description": "ID of the project for which to list BuildTriggers.",
187 "location": "path",
188 "required": true,
189 "type": "string"
190 }
191 },
192 "path": "v1/projects/{projectId}/triggers",
193 "response": {
194 "$ref": "ListBuildTriggersResponse"
195 },
196 "scopes": [
197 "https://www.googleapis.com/auth/cloud-platform"
198 ]
199 },
200 "delete": {
201 "description": "Deletes an BuildTrigger by its proje ct ID and trigger ID.\n\nThis API is experimental.",
202 "httpMethod": "DELETE",
203 "id": "cloudbuild.projects.triggers.delete",
204 "parameterOrder": [
205 "projectId",
206 "triggerId"
207 ],
208 "parameters": {
209 "projectId": {
210 "description": "ID of the project that owns the trigger.",
211 "location": "path",
212 "required": true,
213 "type": "string"
214 },
215 "triggerId": {
216 "description": "ID of the BuildTrigger to de lete.",
217 "location": "path",
218 "required": true,
219 "type": "string"
220 }
221 },
222 "path": "v1/projects/{projectId}/triggers/{triggerId }",
223 "response": {
224 "$ref": "Empty"
225 },
226 "scopes": [
227 "https://www.googleapis.com/auth/cloud-platform"
228 ]
229 },
230 "patch": {
231 "description": "Updates an BuildTrigger by its proje ct ID and trigger ID.\n\nThis API is experimental.",
232 "httpMethod": "PATCH",
233 "id": "cloudbuild.projects.triggers.patch",
234 "parameterOrder": [
235 "projectId",
236 "triggerId"
237 ],
238 "parameters": {
239 "projectId": {
240 "description": "ID of the project that owns the trigger.",
241 "location": "path",
242 "required": true,
243 "type": "string"
244 },
245 "triggerId": {
246 "description": "ID of the BuildTrigger to up date.",
247 "location": "path",
248 "required": true,
249 "type": "string"
250 }
251 },
252 "path": "v1/projects/{projectId}/triggers/{triggerId }",
253 "request": {
254 "$ref": "BuildTrigger"
255 },
256 "response": {
257 "$ref": "BuildTrigger"
258 },
259 "scopes": [
260 "https://www.googleapis.com/auth/cloud-platform"
261 ]
262 }
263 }
264 },
119 "builds": { 265 "builds": {
120 "methods": { 266 "methods": {
121 "create": { 267 "create": {
122 "description": "Starts a build with the specified co nfiguration.\n\nThe long-running Operation returned by this method will include the ID of\nthe build, which can be passed to GetBuild to determine its status (e .g.,\nsuccess or failure).", 268 "description": "Starts a build with the specified co nfiguration.\n\nThe long-running Operation returned by this method will include the ID of\nthe build, which can be passed to GetBuild to determine its status (e .g.,\nsuccess or failure).",
123 "httpMethod": "POST", 269 "httpMethod": "POST",
124 "id": "cloudbuild.projects.builds.create", 270 "id": "cloudbuild.projects.builds.create",
125 "parameterOrder": [ 271 "parameterOrder": [
126 "projectId" 272 "projectId"
127 ], 273 ],
128 "parameters": { 274 "parameters": {
(...skipping 178 matching lines...) Expand 10 before | Expand all | Expand 10 after
307 "response": { 453 "response": {
308 "$ref": "ListOperationsResponse" 454 "$ref": "ListOperationsResponse"
309 }, 455 },
310 "scopes": [ 456 "scopes": [
311 "https://www.googleapis.com/auth/cloud-platform" 457 "https://www.googleapis.com/auth/cloud-platform"
312 ] 458 ]
313 } 459 }
314 } 460 }
315 } 461 }
316 }, 462 },
317 "revision": "20160804", 463 "revision": "20160825",
318 "rootUrl": "https://cloudbuild.googleapis.com/", 464 "rootUrl": "https://cloudbuild.googleapis.com/",
319 "schemas": { 465 "schemas": {
320 "Status": { 466 "Status": {
321 "description": "The `Status` type defines a logical error model that is suitable for different\nprogramming environments, including REST APIs and RP C APIs. It is used by\n[gRPC](https://github.com/grpc). The error model is desig ned to be:\n\n- Simple to use and understand for most users\n- Flexible enough t o meet unexpected needs\n\n# Overview\n\nThe `Status` message contains three pie ces of data: error code, error message,\nand error details. The error code shoul d be an enum value of\ngoogle.rpc.Code, but it may accept additional error codes if needed. The\nerror message should be a developer-facing English message tha t helps\ndevelopers *understand* and *resolve* the error. If a localized user-fa cing\nerror message is needed, put the localized message in the error details or \nlocalize it in the client. The optional error details may contain arbitrary\ni nformation about the error. There is a predefined set of error detail types\nin the package `google.rpc` which can be used for common error conditions.\n\n# Lan guage mapping\n\nThe `Status` message is the logical representation of the error model, but it\nis not necessarily the actual wire format. When the `Status` mes sage is\nexposed in different client libraries and different wire protocols, it can be\nmapped differently. For example, it will likely be mapped to some except ions\nin Java, but more likely mapped to some error codes in C.\n\n# Other uses\ n\nThe error model and the `Status` message can be used in a variety of\nenviron ments, either with or without APIs, to provide a\nconsistent developer experienc e across different environments.\n\nExample uses of this error model include:\n\ n- Partial errors. If a service needs to return partial errors to the client,\n it may embed the `Status` in the normal response to indicate the partial\n errors.\n\n- Workflow errors. A typical workflow has multiple steps. Each step may\n have a `Status` message for error reporting purpose.\n\n- Batch operati ons. If a client uses batch request and batch response, the\n `Status` messag e should be used directly inside batch response, one for\n each error sub-res ponse.\n\n- Asynchronous operations. If an API call embeds asynchronous operatio n\n results in its response, the status of those operations should be\n re presented directly using the `Status` message.\n\n- Logging. If some API errors are stored in logs, the message `Status` could\n be used directly after any s tripping needed for security/privacy reasons.", 467 "description": "The `Status` type defines a logical error model that is suitable for different\nprogramming environments, including REST APIs and RP C APIs. It is used by\n[gRPC](https://github.com/grpc). The error model is desig ned to be:\n\n- Simple to use and understand for most users\n- Flexible enough t o meet unexpected needs\n\n# Overview\n\nThe `Status` message contains three pie ces of data: error code, error message,\nand error details. The error code shoul d be an enum value of\ngoogle.rpc.Code, but it may accept additional error codes if needed. The\nerror message should be a developer-facing English message tha t helps\ndevelopers *understand* and *resolve* the error. If a localized user-fa cing\nerror message is needed, put the localized message in the error details or \nlocalize it in the client. The optional error details may contain arbitrary\ni nformation about the error. There is a predefined set of error detail types\nin the package `google.rpc` which can be used for common error conditions.\n\n# Lan guage mapping\n\nThe `Status` message is the logical representation of the error model, but it\nis not necessarily the actual wire format. When the `Status` mes sage is\nexposed in different client libraries and different wire protocols, it can be\nmapped differently. For example, it will likely be mapped to some except ions\nin Java, but more likely mapped to some error codes in C.\n\n# Other uses\ n\nThe error model and the `Status` message can be used in a variety of\nenviron ments, either with or without APIs, to provide a\nconsistent developer experienc e across different environments.\n\nExample uses of this error model include:\n\ n- Partial errors. If a service needs to return partial errors to the client,\n it may embed the `Status` in the normal response to indicate the partial\n errors.\n\n- Workflow errors. A typical workflow has multiple steps. Each step may\n have a `Status` message for error reporting purpose.\n\n- Batch operati ons. If a client uses batch request and batch response, the\n `Status` messag e should be used directly inside batch response, one for\n each error sub-res ponse.\n\n- Asynchronous operations. If an API call embeds asynchronous operatio n\n results in its response, the status of those operations should be\n re presented directly using the `Status` message.\n\n- Logging. If some API errors are stored in logs, the message `Status` could\n be used directly after any s tripping needed for security/privacy reasons.",
322 "id": "Status", 468 "id": "Status",
323 "properties": { 469 "properties": {
324 "code": { 470 "code": {
325 "description": "The status code, which should be an enum val ue of google.rpc.Code.", 471 "description": "The status code, which should be an enum val ue of google.rpc.Code.",
326 "format": "int32", 472 "format": "int32",
327 "type": "integer" 473 "type": "integer"
(...skipping 92 matching lines...) Expand 10 before | Expand all | Expand 10 after
420 "description": "The normal response of the operation in case of success. If the original\nmethod returns no data on success, such as `Delet e`, the response is\n`google.protobuf.Empty`. If the original method is standar d\n`Get`/`Create`/`Update`, the response should be the resource. For other\nmet hods, the response should have the type `XxxResponse`, where `Xxx`\nis the origi nal method name. For example, if the original method name\nis `TakeSnapshot()`, the inferred response type is\n`TakeSnapshotResponse`.", 566 "description": "The normal response of the operation in case of success. If the original\nmethod returns no data on success, such as `Delet e`, the response is\n`google.protobuf.Empty`. If the original method is standar d\n`Get`/`Create`/`Update`, the response should be the resource. For other\nmet hods, the response should have the type `XxxResponse`, where `Xxx`\nis the origi nal method name. For example, if the original method name\nis `TakeSnapshot()`, the inferred response type is\n`TakeSnapshotResponse`.",
421 "type": "object" 567 "type": "object"
422 }, 568 },
423 "name": { 569 "name": {
424 "description": "The server-assigned name, which is only uniq ue within the same service that\noriginally returns it. If you use the default H TTP mapping, the\n`name` should have the format of `operations/some/unique/name` .", 570 "description": "The server-assigned name, which is only uniq ue within the same service that\noriginally returns it. If you use the default H TTP mapping, the\n`name` should have the format of `operations/some/unique/name` .",
425 "type": "string" 571 "type": "string"
426 } 572 }
427 }, 573 },
428 "type": "object" 574 "type": "object"
429 }, 575 },
576 "BuildTrigger": {
577 "description": "Configuration for an automated build in response to source repository\nchanges.",
578 "id": "BuildTrigger",
579 "properties": {
580 "filename": {
581 "description": "Path, from the source root, to a file whose contents is used for the\ntemplate.",
582 "type": "string"
583 },
584 "triggerTemplate": {
585 "$ref": "RepoSource",
586 "description": "Template describing the types of source chan ges to trigger a build.\n\nBranch and tag names in trigger templates are interpr eted as regular\nexpressions. Any branch or tag change that matches that regular expression\nwill trigger a build."
587 },
588 "build": {
589 "$ref": "Build",
590 "description": "Contents of the build template."
591 },
592 "createTime": {
593 "description": "Time when the trigger was created.\n\n@Outpu tOnly",
594 "format": "google-datetime",
595 "type": "string"
596 },
597 "id": {
598 "description": "Unique identifier of the trigger.\n\n@Output Only",
599 "type": "string"
600 }
601 },
602 "type": "object"
603 },
430 "BuiltImage": { 604 "BuiltImage": {
431 "description": "BuiltImage describes an image built by the pipeline. ", 605 "description": "BuiltImage describes an image built by the pipeline. ",
432 "id": "BuiltImage", 606 "id": "BuiltImage",
433 "properties": { 607 "properties": {
434 "digest": { 608 "digest": {
435 "description": "Docker Registry 2.0 digest.", 609 "description": "Docker Registry 2.0 digest.",
436 "type": "string" 610 "type": "string"
437 }, 611 },
438 "name": { 612 "name": {
439 "description": "Name used to push the container image to Goo gle Container Registry, as\npresented to `docker push`.", 613 "description": "Name used to push the container image to Goo gle Container Registry, as\npresented to `docker push`.",
(...skipping 51 matching lines...) Expand 10 before | Expand all | Expand 10 after
491 "id": "Results", 665 "id": "Results",
492 "properties": { 666 "properties": {
493 "images": { 667 "images": {
494 "description": "Images that were built as a part of the buil d.", 668 "description": "Images that were built as a part of the buil d.",
495 "items": { 669 "items": {
496 "$ref": "BuiltImage" 670 "$ref": "BuiltImage"
497 }, 671 },
498 "type": "array" 672 "type": "array"
499 }, 673 },
500 "buildStepImages": { 674 "buildStepImages": {
501 "description": "List of build step digests, in order corresp onding to build step indices.\nnext id = 4", 675 "description": "List of build step digests, in order corresp onding to build step indices.",
502 "items": { 676 "items": {
503 "type": "string" 677 "type": "string"
504 }, 678 },
505 "type": "array" 679 "type": "array"
506 } 680 }
507 }, 681 },
508 "type": "object" 682 "type": "object"
509 }, 683 },
510 "Build": { 684 "Build": {
511 "description": "A build resource in the Container Builder API.\n\nAt a high level, a Build describes where to find source code, how to build\nit (fo r example, the builder image to run on the source), and what tag to\napply to th e built image when it is pushed to Google Container Registry.", 685 "description": "A build resource in the Container Builder API.\n\nAt a high level, a Build describes where to find source code, how to build\nit (fo r example, the builder image to run on the source), and what tag to\napply to th e built image when it is pushed to Google Container Registry.",
(...skipping 60 matching lines...) Expand 10 before | Expand all | Expand 10 after
572 }, 746 },
573 "source": { 747 "source": {
574 "$ref": "Source", 748 "$ref": "Source",
575 "description": "Describes where to find the source files to build." 749 "description": "Describes where to find the source files to build."
576 }, 750 },
577 "createTime": { 751 "createTime": {
578 "description": "Time at which the build was created.\n@Outpu tOnly", 752 "description": "Time at which the build was created.\n@Outpu tOnly",
579 "format": "google-datetime", 753 "format": "google-datetime",
580 "type": "string" 754 "type": "string"
581 }, 755 },
756 "logUrl": {
757 "description": "URL to logs for this build in Google Cloud L ogging.\n@OutputOnly",
758 "type": "string"
759 },
582 "statusDetail": { 760 "statusDetail": {
583 "description": "Customer-readable message about the current status.\n@OutputOnly", 761 "description": "Customer-readable message about the current status.\n@OutputOnly",
584 "type": "string" 762 "type": "string"
585 }, 763 },
586 "images": { 764 "images": {
587 "description": "List of images expected to be built and push ed to Google Container\nRegistry. If an image is listed here and the image is no t produced by\none of the build steps, the build will fail. Any images present w hen\nthe build steps are complete will be pushed to Container Registry.", 765 "description": "List of images expected to be built and push ed to Google Container\nRegistry. If an image is listed here and the image is no t produced by\none of the build steps, the build will fail. Any images present w hen\nthe build steps are complete will be pushed to Container Registry.",
588 "items": { 766 "items": {
589 "type": "string" 767 "type": "string"
590 }, 768 },
591 "type": "array" 769 "type": "array"
592 }, 770 },
593 "startTime": { 771 "startTime": {
594 "description": "Time at which execution of the build was sta rted.\n@OutputOnly", 772 "description": "Time at which execution of the build was sta rted.\n@OutputOnly",
595 "format": "google-datetime", 773 "format": "google-datetime",
596 "type": "string" 774 "type": "string"
597 }, 775 },
598 "logsBucket": { 776 "logsBucket": {
599 "description": "Google Cloud Storage bucket where logs shoul d be written (see\n[Bucket Name\nRequirements](https://cloud.google.com/storage/ docs/bucket-naming#requirements)).\nLogs file names will be of the format `${log s_bucket}/log-${build_id}.txt`.", 777 "description": "Google Cloud Storage bucket where logs shoul d be written (see\n[Bucket Name\nRequirements](https://cloud.google.com/storage/ docs/bucket-naming#requirements)).\nLogs file names will be of the format `${log s_bucket}/log-${build_id}.txt`.",
600 "type": "string" 778 "type": "string"
601 }, 779 },
602 "projectId": { 780 "projectId": {
603 "description": "ID of the project.\n@OutputOnly.", 781 "description": "ID of the project.\n@OutputOnly.",
604 "type": "string" 782 "type": "string"
605 } 783 }
606 }, 784 },
607 "type": "object" 785 "type": "object"
608 }, 786 },
787 "ListBuildTriggersResponse": {
788 "description": "Response containing existing BuildTriggers.",
789 "id": "ListBuildTriggersResponse",
790 "properties": {
791 "triggers": {
792 "description": "BuildTriggers for the project, sorted by cre ate_time descending.",
793 "items": {
794 "$ref": "BuildTrigger"
795 },
796 "type": "array"
797 }
798 },
799 "type": "object"
800 },
609 "CancelBuildRequest": { 801 "CancelBuildRequest": {
610 "description": "Request to cancel an ongoing build.", 802 "description": "Request to cancel an ongoing build.",
611 "id": "CancelBuildRequest", 803 "id": "CancelBuildRequest",
612 "properties": {}, 804 "properties": {},
613 "type": "object" 805 "type": "object"
614 }, 806 },
615 "FileHashes": { 807 "FileHashes": {
616 "description": "Container message for hashes of byte content of file s, used in\nSourceProvenance messages to verify integrity of source input to the build.", 808 "description": "Container message for hashes of byte content of file s, used in\nSourceProvenance messages to verify integrity of source input to the build.",
617 "id": "FileHashes", 809 "id": "FileHashes",
618 "properties": { 810 "properties": {
(...skipping 85 matching lines...) Expand 10 before | Expand all | Expand 10 after
704 "description": "Name of the container image to use for creat ing this stage in the\npipeline, as presented to `docker pull`.", 896 "description": "Name of the container image to use for creat ing this stage in the\npipeline, as presented to `docker pull`.",
705 "type": "string" 897 "type": "string"
706 }, 898 },
707 "dir": { 899 "dir": {
708 "description": "Working directory (relative to project sourc e root) to use when running\nthis operation's container.", 900 "description": "Working directory (relative to project sourc e root) to use when running\nthis operation's container.",
709 "type": "string" 901 "type": "string"
710 } 902 }
711 }, 903 },
712 "type": "object" 904 "type": "object"
713 }, 905 },
906 "Empty": {
907 "description": "A generic empty message that you can re-use to avoid defining duplicated\nempty messages in your APIs. A typical example is to use i t as the request\nor the response type of an API method. For instance:\n\n se rvice Foo {\n rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty );\n }\n\nThe JSON representation for `Empty` is empty JSON object `{}`.",
908 "id": "Empty",
909 "properties": {},
910 "type": "object"
911 },
714 "BuildOptions": { 912 "BuildOptions": {
715 "description": "Optional arguments to enable specific features of bu ilds.", 913 "description": "Optional arguments to enable specific features of bu ilds.",
716 "id": "BuildOptions", 914 "id": "BuildOptions",
717 "properties": { 915 "properties": {
718 "sourceProvenanceHash": { 916 "sourceProvenanceHash": {
719 "description": "Requested hash for SourceProvenance.", 917 "description": "Requested hash for SourceProvenance.",
720 "enumDescriptions": [ 918 "enumDescriptions": [
721 "No hash requested.", 919 "No hash requested.",
722 "Use a sha256 hash." 920 "Use a sha256 hash."
723 ], 921 ],
(...skipping 37 matching lines...) Expand 10 before | Expand all | Expand 10 after
761 "type": "array" 959 "type": "array"
762 } 960 }
763 }, 961 },
764 "type": "object" 962 "type": "object"
765 } 963 }
766 }, 964 },
767 "servicePath": "", 965 "servicePath": "",
768 "title": "Google Cloud Container Builder API", 966 "title": "Google Cloud Container Builder API",
769 "version": "v1" 967 "version": "v1"
770 } 968 }
OLDNEW
« no previous file with comments | « discovery/googleapis/classroom__v1.json ('k') | discovery/googleapis/clouddebugger__v2.json » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698