Michaël Zasso
Michaël Zasso
> Add echo statements in promotion script I added `set -x` to all relevant scripts.
Status: the script is currently runnning `aws s3 cp /home/dist/nodejs/release/v20.10.0/ s3://dist-prod/nodejs/release/v20.10.0/ ...` and that's taking a long time (with no feedback to the console).
And it just started to fail with the "EOF occurred in violation of protocol" error 😭
@richardlau I think your hunch was right. The release puts a high load on the server and it takes to long to send the files to R2 (we probably hit...
I disabled the upload script, signed the release, and re-synced the folder manually to R2.
To avoid semver-major and allow early testing, this could be exposed from a builtin module and only added as a global later.
It's probably the opposite: I guess GCC was updated in the GitHub runners since the last push (two months ago) and includes new warnings.
I'm taking care of the jenkins-workspace hosts.
I thought the goal was to have a sort of rsync? I don't see how this implementation will work with the release workflow, which includes a manual promomotion step from...