@googleapis/toolresults 1.0.0 → 2.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,23 @@
1
1
  # Changelog
2
2
 
3
+ ## [2.0.0](https://github.com/googleapis/google-api-nodejs-client/compare/toolresults-v1.0.1...toolresults-v2.0.0) (2023-04-08)
4
+
5
+
6
+ ### ⚠ BREAKING CHANGES
7
+
8
+ * This release has breaking changes.
9
+
10
+ ### Features
11
+
12
+ * run the generator ([#3203](https://github.com/googleapis/google-api-nodejs-client/issues/3203)) ([713224f](https://github.com/googleapis/google-api-nodejs-client/commit/713224fe0271843ea61b5d5cbd434ed2aa7b4d69))
13
+
14
+ ## [1.0.1](https://github.com/googleapis/google-api-nodejs-client/compare/toolresults-v1.0.0...toolresults-v1.0.1) (2023-02-10)
15
+
16
+
17
+ ### Bug Fixes
18
+
19
+ * **toolresults:** update the API ([656c975](https://github.com/googleapis/google-api-nodejs-client/commit/656c9754fde6b7d46238b0873ebe1f1acb7501f3))
20
+
3
21
  ## [1.0.0](https://github.com/googleapis/google-api-nodejs-client/compare/toolresults-v0.4.1...toolresults-v1.0.0) (2022-10-28)
4
22
 
5
23
 
@@ -360,7 +360,7 @@ export declare namespace toolresults_v1beta3 {
360
360
  value?: string | null;
361
361
  }
362
362
  /**
363
- * An Execution represents a collection of Steps. For instance, it could represent: - a mobile test executed across a range of device configurations - a jenkins job with a build step followed by a test step The maximum size of an execution message is 1 MiB. An Execution can be updated until its state is set to COMPLETE at which point it becomes immutable.
363
+ * An Execution represents a collection of Steps. For instance, it could represent: - a mobile test executed across a range of device configurations - a jenkins job with a build step followed by a test step The maximum size of an execution message is 1 MiB. An Execution can be updated until its state is set to COMPLETE at which point it becomes immutable. Next tag: 16
364
364
  */
365
365
  export interface Schema$Execution {
366
366
  /**
@@ -1297,7 +1297,7 @@ export declare namespace toolresults_v1beta3 {
1297
1297
  message?: string | null;
1298
1298
  }
1299
1299
  /**
1300
- * A Step represents a single operation performed as part of Execution. A step can be used to represent the execution of a tool ( for example a test runner execution or an execution of a compiler). Steps can overlap (for instance two steps might have the same start time if some operations are done in parallel). Here is an example, let's consider that we have a continuous build is executing a test runner for each iteration. The workflow would look like: - user creates a Execution with id 1 - user creates an TestExecutionStep with id 100 for Execution 1 - user update TestExecutionStep with id 100 to add a raw xml log + the service parses the xml logs and returns a TestExecutionStep with updated TestResult(s). - user update the status of TestExecutionStep with id 100 to COMPLETE A Step can be updated until its state is set to COMPLETE at which points it becomes immutable. Next tag: 27
1300
+ * A Step represents a single operation performed as part of Execution. A step can be used to represent the execution of a tool ( for example a test runner execution or an execution of a compiler). Steps can overlap (for instance two steps might have the same start time if some operations are done in parallel). Here is an example, let's consider that we have a continuous build is executing a test runner for each iteration. The workflow would look like: - user creates a Execution with id 1 - user creates a TestExecutionStep with id 100 for Execution 1 - user update TestExecutionStep with id 100 to add a raw xml log + the service parses the xml logs and returns a TestExecutionStep with updated TestResult(s). - user update the status of TestExecutionStep with id 100 to COMPLETE A Step can be updated until its state is set to COMPLETE at which points it becomes immutable. Next tag: 27
1301
1301
  */
1302
1302
  export interface Schema$Step {
1303
1303
  /**
@@ -3318,7 +3318,7 @@ export declare namespace toolresults_v1beta3 {
3318
3318
  patch(params: Params$Resource$Projects$Histories$Executions$Steps$Patch, callback: BodyResponseCallback<Schema$Step>): void;
3319
3319
  patch(callback: BodyResponseCallback<Schema$Step>): void;
3320
3320
  /**
3321
- * Publish xml files to an existing Step. May return any of the following canonical error codes: - PERMISSION_DENIED - if the user is not authorized to write project - INVALID_ARGUMENT - if the request is malformed - FAILED_PRECONDITION - if the requested state transition is illegal, e.g try to upload a duplicate xml file or a file too large. - NOT_FOUND - if the containing Execution does not exist
3321
+ * Publish xml files to an existing Step. May return any of the following canonical error codes: - PERMISSION_DENIED - if the user is not authorized to write project - INVALID_ARGUMENT - if the request is malformed - FAILED_PRECONDITION - if the requested state transition is illegal, e.g. try to upload a duplicate xml file or a file too large. - NOT_FOUND - if the containing Execution does not exist
3322
3322
  * @example
3323
3323
  * ```js
3324
3324
  * // Before running the sample:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@googleapis/toolresults",
3
- "version": "1.0.0",
3
+ "version": "2.0.0",
4
4
  "description": "toolresults",
5
5
  "main": "build/index.js",
6
6
  "types": "build/index.d.ts",
@@ -38,6 +38,6 @@
38
38
  "ts-loader": "^9.0.0",
39
39
  "typescript": "~4.8.4",
40
40
  "webpack": "^5.0.0",
41
- "webpack-cli": "^4.0.0"
41
+ "webpack-cli": "^5.0.0"
42
42
  }
43
43
  }
package/v1beta3.ts CHANGED
@@ -409,7 +409,7 @@ export namespace toolresults_v1beta3 {
409
409
  value?: string | null;
410
410
  }
411
411
  /**
412
- * An Execution represents a collection of Steps. For instance, it could represent: - a mobile test executed across a range of device configurations - a jenkins job with a build step followed by a test step The maximum size of an execution message is 1 MiB. An Execution can be updated until its state is set to COMPLETE at which point it becomes immutable.
412
+ * An Execution represents a collection of Steps. For instance, it could represent: - a mobile test executed across a range of device configurations - a jenkins job with a build step followed by a test step The maximum size of an execution message is 1 MiB. An Execution can be updated until its state is set to COMPLETE at which point it becomes immutable. Next tag: 16
413
413
  */
414
414
  export interface Schema$Execution {
415
415
  /**
@@ -1337,7 +1337,7 @@ export namespace toolresults_v1beta3 {
1337
1337
  message?: string | null;
1338
1338
  }
1339
1339
  /**
1340
- * A Step represents a single operation performed as part of Execution. A step can be used to represent the execution of a tool ( for example a test runner execution or an execution of a compiler). Steps can overlap (for instance two steps might have the same start time if some operations are done in parallel). Here is an example, let's consider that we have a continuous build is executing a test runner for each iteration. The workflow would look like: - user creates a Execution with id 1 - user creates an TestExecutionStep with id 100 for Execution 1 - user update TestExecutionStep with id 100 to add a raw xml log + the service parses the xml logs and returns a TestExecutionStep with updated TestResult(s). - user update the status of TestExecutionStep with id 100 to COMPLETE A Step can be updated until its state is set to COMPLETE at which points it becomes immutable. Next tag: 27
1340
+ * A Step represents a single operation performed as part of Execution. A step can be used to represent the execution of a tool ( for example a test runner execution or an execution of a compiler). Steps can overlap (for instance two steps might have the same start time if some operations are done in parallel). Here is an example, let's consider that we have a continuous build is executing a test runner for each iteration. The workflow would look like: - user creates a Execution with id 1 - user creates a TestExecutionStep with id 100 for Execution 1 - user update TestExecutionStep with id 100 to add a raw xml log + the service parses the xml logs and returns a TestExecutionStep with updated TestResult(s). - user update the status of TestExecutionStep with id 100 to COMPLETE A Step can be updated until its state is set to COMPLETE at which points it becomes immutable. Next tag: 27
1341
1341
  */
1342
1342
  export interface Schema$Step {
1343
1343
  /**
@@ -4866,7 +4866,7 @@ export namespace toolresults_v1beta3 {
4866
4866
  }
4867
4867
 
4868
4868
  /**
4869
- * Publish xml files to an existing Step. May return any of the following canonical error codes: - PERMISSION_DENIED - if the user is not authorized to write project - INVALID_ARGUMENT - if the request is malformed - FAILED_PRECONDITION - if the requested state transition is illegal, e.g try to upload a duplicate xml file or a file too large. - NOT_FOUND - if the containing Execution does not exist
4869
+ * Publish xml files to an existing Step. May return any of the following canonical error codes: - PERMISSION_DENIED - if the user is not authorized to write project - INVALID_ARGUMENT - if the request is malformed - FAILED_PRECONDITION - if the requested state transition is illegal, e.g. try to upload a duplicate xml file or a file too large. - NOT_FOUND - if the containing Execution does not exist
4870
4870
  * @example
4871
4871
  * ```js
4872
4872
  * // Before running the sample: