-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
job request: CI testing for GYP3 #1789
Comments
You have my ⚔️ for this. It's been discussed on and off for years but nobody has done it. I'd love to see a node-gyp job in ci and I encourage you to have a go at building it! Just be conscious of security and the risks of running arbitrary code on machines that aren't isolated between runs. |
Gyp != node-gyp. We already have node-gyp testing in https://ci.nodejs.org/view/All/job/nodegyp-test-pull-request/ (which IMO we should extend to cover more platforms). +1 for adding gyp3 testing in the CI. |
Oh well, it just shows how tuned in I am I guess! Well you have my +1 anyway. |
What help is needed? |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
I would like to have a job that does CI testing for GYP3 on the Node.js cluster.
Currently testing in done only on Windows, Ubuntu, and macOS (all on Intel X64). This is only a subset of the platforms supported by node-core. As a result bugs and regressions can only be discovered at the earliest at integration time (e.g. nodejs/node#26620), which significantly slows down the development cycle.
Although GYP/GYP3 are not OpenJSF projects, they are is still very important for the development on node-core, and are paramount for the Node.js ecosystem via
node-gyp
.The text was updated successfully, but these errors were encountered: