build
build copied to clipboard
nodejs
Better build and test infra for Node.
We already have this mechanism in place in the test CI. There were some problems with it, but the latest changes from https://github.com/nodejs/build/pull/3514 should fix it all. Since release CI...
Refs: https://github.com/nodejs/node/issues/50079#issuecomment-1752097632 I think that might be the cause behind the `v8-updates/test-linux-perf` failures of the recent V8 update. Currenly https://github.com/nodejs/build/blob/main/ansible/roles/linux-perf/tasks/main.yml pulls the source from the most recent commit from https://github.com/torvalds/linux.git...
Spotted while adjusting the firewall configuration for the `-joyent-` systems. It appears we have a number of entries in the firewall configuration for machines that no longer exist. For example...
openssl 1.1.1 went EOL on September 11, as did node v16. I don't think there's reason to keep the node-test-linux-linked-openssl111 and node-test-linux-linked-openssl111fips bots around and they've been problematic in at...
Currently, benchmark ci run only compares a branch with a pull request id, but issues like regressions between releases require to benchmark a branch (v18.x) with another branch (v16.x). It...
We have two of them in the inventory: - [ ] [test-softlayer-ubuntu1404-x64-1](https://ci.nodejs.org/manage/computer/test-softlayer-ubuntu1404-x64-1/) - [x] [test-digitalocean-ubuntu1404-x64-1](https://ci.nodejs.org/manage/computer/test-digitalocean-ubuntu1404-x64-1/)
https://ci.nodejs.org/label/11.6/
Since v16 went EoL, RHEL8 is used for all release lines. TODO: - Remove from secrets repo - Delete DO droplet
Hey folks, As most of you know, we don't run the benchmarking CI on every release because running all the suites takes days. That's mostly because we rely on a...
