Blog: v14.0.0 release post

[BethGriggs]

Refs: nodejs/node#32181

[BethGriggs]

Hmm, 15minutes is longer than usual for the website to update - is it possible to check the state or force a redeploy? @nodejs/build maybe?

[sam-github]

Its up now, but IIRC, it used to be just minutes before deploying. It was long enough for the last sec announcement, that I just left and checked the next morning.

I wonder if some of the caching changes recently made it slower? cc: @rvagg

[richardlau]

GitHub itself is having issues at the moment which could be a contributing factor.

[richardlau]

The tail from the webhook log (https://nodejs.org/github-webhook.log) seems to indicate it hasn't been triggered for/picked up the changes from this PR:

Sun Apr 19 2020 15:34:06 GMT+0000 (Coordinated Universal Time)
Took 137643 ms
stdout: build-site.sh already running
event="push", match="ref == "refs/heads/master" && repository.full_name == "nodejs/nodejs.org"", exec="/home/nodejs/build-site.sh nodejs"
Tue Apr 21 2020 15:02:06 GMT+0000 (Coordinated Universal Time)
Took 22 ms
stdout: build-site.sh already running
event="push", match="ref == "refs/heads/master" && repository.full_name == "nodejs/nodejs.org"", exec="/home/nodejs/build-site.sh nodejs"
Tue Apr 21 2020 15:02:06 GMT+0000 (Coordinated Universal Time)
Took 11 ms

[richardlau]

The tail from the webhook log (https://nodejs.org/github-webhook.log) seems to indicate it hasn't been triggered for/picked up the changes from this PR:

Sun Apr 19 2020 15:34:06 GMT+0000 (Coordinated Universal Time)
Took 137643 ms
stdout: build-site.sh already running
event="push", match="ref == "refs/heads/master" && repository.full_name == "nodejs/nodejs.org"", exec="/home/nodejs/build-site.sh nodejs"
Tue Apr 21 2020 15:02:06 GMT+0000 (Coordinated Universal Time)
Took 22 ms
stdout: build-site.sh already running
event="push", match="ref == "refs/heads/master" && repository.full_name == "nodejs/nodejs.org"", exec="/home/nodejs/build-site.sh nodejs"
Tue Apr 21 2020 15:02:06 GMT+0000 (Coordinated Universal Time)
Took 11 ms

[nschonni]

If you have access to the box, you can try restarting the hook nodejs/build#2123 (comment)

[nschonni]

There is also #3018 if anyone is feeling ambitious

[rvagg]

We have extended the CDN purge from job so that could be a partial explanation for the slower deploy. I think you can expect up to 30 minutes now for cloudflare to refresh.
Although the webhook log should still be showing an update. I guess this got sorted out since the post is visible now?