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

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

Issue 2226653002: Api-roll 40: 2016-08-08 (Closed) Base URL: git@github.com:dart-lang/googleapis.git@master
Patch Set: Addressed review comments 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
« no previous file with comments | « discovery/googleapis/calendar__v3.json ('k') | discovery/googleapis/compute__v1.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 296 matching lines...) Expand 10 before | Expand all | Expand 10 after
307 "response": { 307 "response": {
308 "$ref": "ListOperationsResponse" 308 "$ref": "ListOperationsResponse"
309 }, 309 },
310 "scopes": [ 310 "scopes": [
311 "https://www.googleapis.com/auth/cloud-platform" 311 "https://www.googleapis.com/auth/cloud-platform"
312 ] 312 ]
313 } 313 }
314 } 314 }
315 } 315 }
316 }, 316 },
317 "revision": "20160714", 317 "revision": "20160804",
318 "rootUrl": "https://cloudbuild.googleapis.com/", 318 "rootUrl": "https://cloudbuild.googleapis.com/",
319 "schemas": { 319 "schemas": {
320 "Status": { 320 "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.", 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.",
322 "id": "Status", 322 "id": "Status",
323 "properties": { 323 "properties": {
324 "code": { 324 "code": {
325 "description": "The status code, which should be an enum val ue of google.rpc.Code.", 325 "description": "The status code, which should be an enum val ue of google.rpc.Code.",
326 "format": "int32", 326 "format": "int32",
327 "type": "integer" 327 "type": "integer"
(...skipping 27 matching lines...) Expand all
355 }, 355 },
356 "type": "object" 356 "type": "object"
357 }, 357 },
358 "Source": { 358 "Source": {
359 "description": "Source describes the location of the source in a sup ported storage\nservice.", 359 "description": "Source describes the location of the source in a sup ported storage\nservice.",
360 "id": "Source", 360 "id": "Source",
361 "properties": { 361 "properties": {
362 "storageSource": { 362 "storageSource": {
363 "$ref": "StorageSource", 363 "$ref": "StorageSource",
364 "description": "If provided, get the source from this locati on in in Google Cloud\nStorage." 364 "description": "If provided, get the source from this locati on in in Google Cloud\nStorage."
365 },
366 "repoSource": {
367 "$ref": "RepoSource",
368 "description": "If provided, get source from this location i n a Cloud Repo."
365 } 369 }
366 }, 370 },
367 "type": "object" 371 "type": "object"
368 }, 372 },
369 "SourceProvenance": { 373 "SourceProvenance": {
370 "description": "Provenance of the source. Ways to find the original source, or verify that\nsome source was used for this build.", 374 "description": "Provenance of the source. Ways to find the original source, or verify that\nsome source was used for this build.",
371 "id": "SourceProvenance", 375 "id": "SourceProvenance",
372 "properties": { 376 "properties": {
377 "resolvedRepoSource": {
378 "$ref": "RepoSource",
379 "description": "A copy of the build's source.repo_source, if exists, with any\nrevisions resolved."
380 },
381 "resolvedStorageSource": {
382 "$ref": "StorageSource",
383 "description": "A copy of the build's source.storage_source, if exists, with any\ngenerations resolved."
384 },
373 "fileHashes": { 385 "fileHashes": {
374 "additionalProperties": { 386 "additionalProperties": {
375 "$ref": "FileHashes" 387 "$ref": "FileHashes"
376 }, 388 },
377 "description": "Hash(es) of the build source, which can be u sed to verify that the original\nsource integrity was maintained in the build. N ote that FileHashes will\nonly be populated if BuildOptions has requested a Sour ceProvenanceHash.\n\nThe keys to this map are file paths used as build source an d the values\ncontain the hash values for those files.\n\nIf the build source ca me in a single package such as a gzipped tarfile\n(.tar.gz), the FileHash will b e for the single path to that file.\n@OutputOnly", 389 "description": "Hash(es) of the build source, which can be u sed to verify that the original\nsource integrity was maintained in the build. N ote that FileHashes will\nonly be populated if BuildOptions has requested a Sour ceProvenanceHash.\n\nThe keys to this map are file paths used as build source an d the values\ncontain the hash values for those files.\n\nIf the build source ca me in a single package such as a gzipped tarfile\n(.tar.gz), the FileHash will b e for the single path to that file.\n@OutputOnly",
378 "type": "object" 390 "type": "object"
379 } 391 }
380 }, 392 },
381 "type": "object" 393 "type": "object"
382 }, 394 },
(...skipping 94 matching lines...) Expand 10 before | Expand all | Expand 10 after
477 "Results": { 489 "Results": {
478 "description": "Results describes the artifacts created by the build pipeline.", 490 "description": "Results describes the artifacts created by the build pipeline.",
479 "id": "Results", 491 "id": "Results",
480 "properties": { 492 "properties": {
481 "images": { 493 "images": {
482 "description": "Images that were built as a part of the buil d.", 494 "description": "Images that were built as a part of the buil d.",
483 "items": { 495 "items": {
484 "$ref": "BuiltImage" 496 "$ref": "BuiltImage"
485 }, 497 },
486 "type": "array" 498 "type": "array"
499 },
500 "buildStepImages": {
501 "description": "List of build step digests, in order corresp onding to build step indices.\nnext id = 4",
502 "items": {
503 "type": "string"
504 },
505 "type": "array"
487 } 506 }
488 }, 507 },
489 "type": "object" 508 "type": "object"
490 }, 509 },
491 "Build": { 510 "Build": {
492 "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.", 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.",
493 "id": "Build", 512 "id": "Build",
494 "properties": { 513 "properties": {
495 "id": { 514 "id": {
496 "description": "Unique identifier of the build.\n@OutputOnly ", 515 "description": "Unique identifier of the build.\n@OutputOnly ",
(...skipping 22 matching lines...) Expand all
519 ], 538 ],
520 "enumDescriptions": [ 539 "enumDescriptions": [
521 "Status of the build is unknown.", 540 "Status of the build is unknown.",
522 "Build has been received and is being queued.", 541 "Build has been received and is being queued.",
523 "Build is queued; work has not yet begun.", 542 "Build is queued; work has not yet begun.",
524 "Build is being executed.", 543 "Build is being executed.",
525 "Build finished successfully.", 544 "Build finished successfully.",
526 "Build failed to complete successfully.", 545 "Build failed to complete successfully.",
527 "Build failed due to an internal cause.", 546 "Build failed due to an internal cause.",
528 "Build took longer than was allowed.", 547 "Build took longer than was allowed.",
529 "Build was canceled by a user.\nnext_id = 9" 548 "Build was canceled by a user."
530 ], 549 ],
531 "type": "string" 550 "type": "string"
532 }, 551 },
533 "options": { 552 "options": {
534 "$ref": "BuildOptions", 553 "$ref": "BuildOptions",
535 "description": "Special options for this build." 554 "description": "Special options for this build."
536 }, 555 },
537 "finishTime": { 556 "finishTime": {
538 "description": "Time at which execution of the build was fin ished.\n@OutputOnly", 557 "description": "Time at which execution of the build was fin ished.\n@OutputOnly",
539 "format": "google-datetime", 558 "format": "google-datetime",
(...skipping 78 matching lines...) Expand 10 before | Expand all | Expand 10 after
618 "operations": { 637 "operations": {
619 "description": "A list of operations that matches the specif ied filter in the request.", 638 "description": "A list of operations that matches the specif ied filter in the request.",
620 "items": { 639 "items": {
621 "$ref": "Operation" 640 "$ref": "Operation"
622 }, 641 },
623 "type": "array" 642 "type": "array"
624 } 643 }
625 }, 644 },
626 "type": "object" 645 "type": "object"
627 }, 646 },
647 "RepoSource": {
648 "description": "RepoSource describes the location of the source in a Google Cloud Source\nRepository.",
649 "id": "RepoSource",
650 "properties": {
651 "repoName": {
652 "description": "Name of the repo. If omitted, the name \"def ault\" is assumed.",
653 "type": "string"
654 },
655 "tagName": {
656 "description": "Name of the tag to build.",
657 "type": "string"
658 },
659 "projectId": {
660 "description": "ID of the project that owns the repo. If omi tted, the project ID requesting\nthe build is assumed.",
661 "type": "string"
662 },
663 "branchName": {
664 "description": "Name of the branch to build.",
665 "type": "string"
666 },
667 "commitSha": {
668 "description": "Explicit commit SHA to build.",
669 "type": "string"
670 }
671 },
672 "type": "object"
673 },
628 "BuildStep": { 674 "BuildStep": {
629 "description": "BuildStep describes a step to perform in the build p ipeline.", 675 "description": "BuildStep describes a step to perform in the build p ipeline.",
630 "id": "BuildStep", 676 "id": "BuildStep",
631 "properties": { 677 "properties": {
678 "id": {
679 "description": "Optional unique identifier for this build st ep, used in wait_for to\nreference this build step as a dependency.",
680 "type": "string"
681 },
682 "env": {
683 "description": "Additional environment variables to set for this step's container.",
684 "items": {
685 "type": "string"
686 },
687 "type": "array"
688 },
689 "waitFor": {
690 "description": "The ID(s) of the step(s) that this build ste p depends on.\nThis build step will not start until all the build steps in wait_ for\nhave completed successfully. If wait_for is empty, this build step will\nst art when all previous build steps in the Build.Steps list have completed\nsucces sfully.",
691 "items": {
692 "type": "string"
693 },
694 "type": "array"
695 },
632 "args": { 696 "args": {
633 "description": "Command-line arguments to use when running t his step's container.", 697 "description": "Command-line arguments to use when running t his step's container.",
634 "items": { 698 "items": {
635 "type": "string" 699 "type": "string"
636 }, 700 },
637 "type": "array" 701 "type": "array"
638 }, 702 },
639 "dir": {
640 "description": "Working directory (relative to project sourc e root) to use when running\nthis operation's container.",
641 "type": "string"
642 },
643 "name": { 703 "name": {
644 "description": "Name of the container image to use for creat ing this stage in the\npipeline, as presented to `docker pull`.", 704 "description": "Name of the container image to use for creat ing this stage in the\npipeline, as presented to `docker pull`.",
645 "type": "string" 705 "type": "string"
646 }, 706 },
647 "env": { 707 "dir": {
648 "description": "Additional environment variables to set for this step's container.", 708 "description": "Working directory (relative to project sourc e root) to use when running\nthis operation's container.",
649 "items": { 709 "type": "string"
650 "type": "string"
651 },
652 "type": "array"
653 } 710 }
654 }, 711 },
655 "type": "object" 712 "type": "object"
656 }, 713 },
657 "BuildOptions": { 714 "BuildOptions": {
658 "description": "Optional arguments to enable specific features of bu ilds.", 715 "description": "Optional arguments to enable specific features of bu ilds.",
659 "id": "BuildOptions", 716 "id": "BuildOptions",
660 "properties": { 717 "properties": {
661 "sourceProvenanceHash": { 718 "sourceProvenanceHash": {
662 "description": "Requested hash for SourceProvenance.", 719 "description": "Requested hash for SourceProvenance.",
(...skipping 41 matching lines...) Expand 10 before | Expand all | Expand 10 after
704 "type": "array" 761 "type": "array"
705 } 762 }
706 }, 763 },
707 "type": "object" 764 "type": "object"
708 } 765 }
709 }, 766 },
710 "servicePath": "", 767 "servicePath": "",
711 "title": "Google Cloud Container Builder API", 768 "title": "Google Cloud Container Builder API",
712 "version": "v1" 769 "version": "v1"
713 } 770 }
OLDNEW
« no previous file with comments | « discovery/googleapis/calendar__v3.json ('k') | discovery/googleapis/compute__v1.json » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698