Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign updoc: replace deprecated CI job #21938
Conversation
This comment has been minimized.
This comment has been minimized.
nodejs-github-bot
added
the
doc
label
Jul 22, 2018
vsemozhetbyt
added
the
meta
label
Jul 22, 2018
This comment has been minimized.
This comment has been minimized.
|
Not sure if this should be approved by the TSC or any other WG. Please, cc or label as seems appropriate. |
This comment has been minimized.
This comment has been minimized.
|
Node.js Collaborators, please, add |
richardlau
approved these changes
Jul 22, 2018
|
Comment is non-blocking for me. |
| @@ -213,7 +213,7 @@ needs to be pointed out separately during the onboarding. | |||
| * Optionally, include your personal pronouns. | |||
| * Label your pull request with the `doc` and `notable-change` labels. | |||
| * Run CI on the PR. Because the PR does not affect any code, use the | |||
| `node-test-pull-request-lite` CI task. Alternatively, use the usual | |||
| `node-test-pull-request-lite-pipeline` CI task. Alternatively, use the usual | |||
| `node-test-pull-request` CI task and cancel it after the linter and one other | |||
| subtask have passed. | |||
This comment has been minimized.
This comment has been minimized.
richardlau
Jul 22, 2018
Member
Maybe one for @nodejs/build to comment on, but my own experience with Jenkins is that cancelling jobs can sometimes leave workspaces in a bad state (usually manifesting in git checkout errors on subsequent runs) depending on where the job was at at the time it was cancelled so I'm not generally in favour of encouraging the cancellation of jobs.
This comment has been minimized.
This comment has been minimized.
maclover7
Jul 23, 2018
Member
From my personal experience, a lot of git checkout errors / infra failures in general with ci.nodejs.org can be linked back to issues with the machine itself, not usually due to cancelling jobs early. Also, you could say there's a benefit from new collaborators practicing how to launch node-test-pull-request jobs. I'd rather folks let the build go all the way through and finish, but I don't think they're "breaking our infra" by cancelling it early.
This comment has been minimized.
This comment has been minimized.
joaocgreis
Jul 23, 2018
Member
I'd prefer that cancelling jobs is not encouraged at all, I've seen a lot of failures because of it. It may not be the most frequent issue but it happens.
At least two cases are know: 1) Abort during a git operation will leave behind a lock file that will make all following jobs on that machine fail; 2) Visual Studio will not stop running immediately after the job is aborted, locking some files and making git clean fail for some time/jobs (happens easily when there are queued jobs). Note that Jenkins does not offer us any reliable way of running anything between jobs, so fixing this is not straightforward.
(To be clear, I'm also not blocking this PR, but would be in favor of deleting the sentence starting at "Alternatively".)
This comment has been minimized.
This comment has been minimized.
vsemozhetbyt
Jul 24, 2018
Author
Member
I will make a new PR after landing to draw more attention to this change.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
cc @nodejs/automation It seems the |
cjihrig
approved these changes
Jul 22, 2018
riyadhalnur
approved these changes
Jul 23, 2018
trivikr
approved these changes
Jul 23, 2018
jasnell
approved these changes
Jul 23, 2018
maclover7
approved these changes
Jul 23, 2018
lpinca
approved these changes
Jul 23, 2018
joaocgreis
approved these changes
Jul 23, 2018
This comment has been minimized.
This comment has been minimized.
|
Landed in c75f36f |
vsemozhetbyt commentedJul 22, 2018
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passesnode-test-pull-request-liteCI job is deprecated now and https://ci.nodejs.org/job/node-test-pull-request-lite/ has this note: "DEPRECATED: please use the node-test-pull-request-lite-pipeline job".