Skip to content
Browse files

doc,meta: allow Travis results for doc/comment changes

Permit the use of Travis CI results for pull requests that only change
documentation or comments. This also removes
node-test-pull-request-lite-pipeline from the documentation. Efforts to
move all CI jobs to pipelines have stalled and it's not clear that our
current Jenkins admins are enthusiastic about pipelines.

PR-URL: #30330
Reviewed-By: Gireesh Punathil <>
Reviewed-By: Jiawen Geng <>
Reviewed-By: Trivikram Kamat <>
Reviewed-By: Colin Ihrig <>
Reviewed-By: Anna Henningsen <>
Reviewed-By: Luigi Pinca <>
  • Loading branch information
Trott authored and MylesBorins committed Nov 8, 2019
1 parent d32cd85 commit fe1296e507b8c85b9a1438881409aa0fec9d48d9
Showing with 3 additions and 6 deletions.
  1. +3 −6
@@ -172,8 +172,9 @@ the comment anyway to avoid any doubt.
All fixes must have a test case which demonstrates the defect. The test should
fail before the change, and pass after the change.

All pull requests must pass continuous integration tests on the
[project CI server](
All pull requests must pass continuous integration tests. Code changes must pass
on [project CI server]( Pull requests that only change
documentation and comments can use Travis CI results.

Do not land any pull requests without passing (green or yellow) CI runs. If
there are CI failures unrelated to the change in the pull request, try "Resume
@@ -187,10 +188,6 @@ everything else.
is the CI job to test pull requests. It runs the `build-ci` and `test-ci`
targets on all supported platforms.

* [`node-test-pull-request-lite-pipeline`](
runs the linter job. It also runs the tests on a very fast host. This is useful
for changes that only affect comments or documentation.

* [`citgm-smoker`](
uses [`CitGM`]( to allow you to run
`npm install && npm test` on a large selection of common modules. This is

0 comments on commit fe1296e

Please sign in to comment.
You can’t perform that action at this time.