14.21.1 security release build stalled

[nschonni]

Looks like the fetch source job failed https://unofficial-builds.nodejs.org/logs/202211042053-v14.21.1/fetch-source.log

+ curl -fsSLO --compressed https://nodejs.org/download/release/v14.21.1/node-v14.21.1.tar.xz
+ [[ release = \r\e\l\e\a\s\e ]]
+ curl -fsSLO --compressed https://nodejs.org/download/release/v14.21.1/node-v14.21.1.tar.xz/../SHASUMS256.txt.asc
curl: (22) The requested URL returned error: 500

That in turn is blocking the docker-node auto-pr for the other release lines

[nschonni]

@richardlau @rvagg not sure if someone can trigger this build again

[nschonni]

@sxa do you have access to reque this? This is blocking the rollout of the security releases for Docker

[nschonni]

@nodejs/build anyone else has access to requeue the job

[sxa]

I was on vacation yesterday so didn't see it - I'll take a look at it now. I wasn't aware the unofficial builds were used by our docker workflows.

[targos]

It's a bit concerning that the Docker releases rely on unofficial builds.

[sxa]

Queued and running now. @nschonni Which of the unofficial builds are mandatory for (thus blocking) the docker releases? I see the musl ones referenced in the linked issue but is that the only one?

[nschonni]

The musl one is the only one used by Docker

[nschonni]

Build succeeded and the automation is working again. Thanks!

[sxa]

Closing, although we should consider the implications of the dependencies of the unofficial builds process in light of this.

[rvagg]

Perhaps we need to give @nschonni or someone else on the docker-node WG access to the machine to trigger rebuilds?