Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blog: v14.0.0 release post #3129

Merged
merged 1 commit into from
Apr 21, 2020
Merged

Conversation

BethGriggs
Copy link
Member

@BethGriggs BethGriggs merged commit c971c02 into nodejs:master Apr 21, 2020
@BethGriggs
Copy link
Member Author

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
Copy link
Contributor

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
Copy link
Member

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

@richardlau
Copy link
Member

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

1 similar comment
@richardlau
Copy link
Member

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
Copy link
Member

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

@nschonni
Copy link
Member

There is also #3018 if anyone is feeling ambitious

@rvagg
Copy link
Member

rvagg commented Apr 21, 2020

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants