|
4 | 4 |
|
5 | 5 | * [Issues and Pull Requests](#issues-and-pull-requests) |
6 | 6 | * [Accepting Modifications](#accepting-modifications) |
| 7 | + - [Useful CI Jobs](#useful-ci-jobs) |
7 | 8 | - [Internal vs. Public API](#internal-vs-public-api) |
8 | 9 | - [Breaking Changes](#breaking-changes) |
9 | 10 | - [Deprecations](#deprecations) |
@@ -87,6 +88,27 @@ All pull requests that modify executable code should be subjected to |
87 | 88 | continuous integration tests on the |
88 | 89 | [project CI server](https://ci.nodejs.org/). |
89 | 90 |
|
| 91 | +#### Useful CI Jobs |
| 92 | + |
| 93 | +* [`node-test-pull-request`](https://ci.nodejs.org/job/node-test-pull-request/) |
| 94 | +is the standard CI run we do to check Pull Requests. It triggers `node-test-commit`, |
| 95 | +which runs the `build-ci` and `test-ci` targets on all supported platforms. |
| 96 | + |
| 97 | +* [`node-test-linter`](https://ci.nodejs.org/job/node-test-linter/) |
| 98 | +only runs the linter targets, which is useful for changes that only affect comments |
| 99 | +or documentation. |
| 100 | + |
| 101 | +* [`citgm-smoker`](https://ci.nodejs.org/job/citgm-smoker/) |
| 102 | +uses [`CitGM`](https://github.com/nodejs/citgm) to allow you to run `npm install && npm test` |
| 103 | +on a large selection of common modules. This is useful to check whether a |
| 104 | +change will cause breakage in the ecosystem. To test Node.JS ABI changes |
| 105 | +you can run [`citgm-abi-smoker`](https://ci.nodejs.org/job/citgm-abi-smoker/). |
| 106 | + |
| 107 | +* [`node-stress-single-test`](https://ci.nodejs.org/job/node-stress-single-test/) |
| 108 | +is designed to allow one to run a group of tests over and over on a specific |
| 109 | +platform to confirm that the test is reliable. |
| 110 | + |
| 111 | + |
90 | 112 | ### Internal vs. Public API |
91 | 113 |
|
92 | 114 | Due to the nature of the JavaScript language, it can often be difficult to |
|
0 commit comments