João Reis

+1 for giving access to both jobs. The build-release job is in the test CI because it is experimental. It doesn't use the release parameters of vcbuild, it's just something...

@ljharb I've sent you login details by email. Please let us know when you no longer need it. Thanks!

Ref https://github.com/nodejs/build/issues/2450 and https://github.com/nodejs/node/issues/25998 There are some releases in https://unofficial-builds.nodejs.org/ . Since it's Windows and can't be built from the docker system that builds for other platforms, I have to...

@atishay working on the releases, they should be done shortly. Will post on https://github.com/nodejs/build/issues/2450 when done. @mhdawson yes I can keep them functional. We cross-compile for ARM64 from our current...

@obastemur you are a member of the node-chakracore team, which means you have run permission in https://ci.nodejs.org/view/All/job/chakracore-test-pull-request/ . Just go there, click "Build with parameters", enter the PR number and...

@obastemur the "Console output" is public on all jobs (logs are only kept for a few days though). I started a run on master: https://ci.nodejs.org/job/chakracore-test/193/ and it is not going...

I'm positive there was some discussion around starting CI from GH comments, but I can't find it. The idea sounds good to me, it's possible that just no one had...

This could be merged to a branch specific for changes that would not outlive this repository, leaving chakracore-master with only changes to be pulled to node. What about creating a...

`DISTTYPE` and `DISTTYPEDIR` are changed to `custom` by the build script when building v8-canaries (and others). The correct variable to use should be `RELEASE_URLBASE`.

PR to add build support: https://github.com/nodejs/llnode/pull/203 . This allows llnode to be easily built on Windows, though actually debugging will require some more work.