You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Get the CI results of PR 12345 (including latest results of each type of
36
-
supported CI) and copy the summaries into clipboard:
35
+
`ncu-ci rate <type>` calculate the success rate for CI jobs in the last 100 runs per [CI Health History](https://github.com/nodejs/reliability#ci-health-history), where `<type>` can be either `pr` for `node-test-pull-request` or `commit` for `node-test-commit`.
`ncu-ci walk <type>` walks CI and displays failures, where `<type>` can be either `pr` for `node-test-pull-request` or `commit` for `node-test-commit`.
Walk the CI for the latest 100 runs of `node-test-pull-request`,
50
-
aggregate the failures, then write the results into a Markdown file,
51
-
and cache the responses from Jenkins so that the next time the command
103
+
1. Walk CI for the latest 100 runs of `node-test-pull-request`,
104
+
aggregate failures, write the results into a Markdown file,
105
+
and then cache the responses from Jenkins so that the next time the command
52
106
is run, it picks up cached data written on disk for jobs whose results
53
107
are known.
54
108
55
-
Note: results are cached in `${ncu_intallation_path}/.ncu/cache`, you
109
+
Note: results are cached in `${ncu_intallation_path}/.ncu/cache`, so you
56
110
may want to clean it up from time to time.
57
111
58
112
```
59
113
ncu-ci walk pr --stats --cache --markdown results.md
60
114
```
61
115
62
-
Walk the CI for the latest 100 runs of `node-test-pull-request`, write the
63
-
failures into a JSON file
116
+
2.Walk CI for the latest 100 runs of `node-test-pull-request`, and then write the
117
+
failures into a JSON file named database.json.
64
118
65
119
```
66
120
ncu-ci walk pr --json database.json
67
121
```
68
122
69
-
Calculate the green rate of the CI for
70
-
[CI Health History](https://github.com/nodejs/reliability#ci-health-history)
123
+
### `ncu-ci pr <jobid>`
124
+
125
+
`ncu-ci pr <jobid>` returns information about the results of a `node-test-pull-request` job.
126
+
127
+
For example, if you would like to see the results of `node-test-pull-request` for https://github.com/nodejs/node/pull/34127, you would visit the PR and note that the `node-test-pull-request` job can be found at https://ci.nodejs.org/job/node-test-pull-request/32158, and therefore the `<jobid>` is `32158`, not `34127`.
`ncu-ci commit <jobid>` returns information about the results of a specified `node-test-commit` job.
150
+
151
+
For example, if you would like to see the results of `node-test-commit` for https://github.com/nodejs/node/pull/34086, you would visit the PR and note that the `node-test-commit` job can be found at https://ci.nodejs.org/job/node-test-commit/39377, and therefore the `<jobid>` is `39377`, not `34086`.
`ncu-ci url <url>` takes a url corresponding to a PR on `nodejs/node`, detects the CI type (either `node-test-commit` or `node-test-pull-request`) and corresponding job id for the latest run, and returns a summary of results about the job run.
175
+
176
+
Example:
177
+
```sh
178
+
node on git:master ❯ ncu-ci url https://github.com/nodejs/node/pull/34127
0 commit comments