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

Latest blog post not showing on nodejs.org #1040

Closed
MylesBorins opened this issue Dec 12, 2017 · 4 comments
Closed

Latest blog post not showing on nodejs.org #1040

MylesBorins opened this issue Dec 12, 2017 · 4 comments
Labels

Comments

@MylesBorins
Copy link
Contributor

Issue on nodejs.org tracker nodejs/nodejs.org#1516

@maclover7
Copy link
Contributor

cc @rvagg

@rvagg
Copy link
Member

rvagg commented Dec 12, 2017

yeah, on it already

@rvagg
Copy link
Member

rvagg commented Dec 12, 2017

Ah, so this was a matter of commits bunching up too close and it refusing to double-process. We don't have a fancy queueing mechanism in place so it just says: if I'm already processing a commit, don't process another.

So I've manually processed it on the server, but this could be done by pushing another commit to HEAD or redelivering the github webhook if you have access to them @ https://github.com/nodejs/nodejs.org/settings/hooks (find the last "push" and redeliver it).

Implementing a queue or a retry-wait might be a good task for someone that knows Bash and wants to contribute: https://github.com/nodejs/build/blob/master/setup/www/resources/scripts/build-site.sh

@MylesBorins
Copy link
Contributor Author

@rvagg do you think it would make sense to document that process in the readme in case anyone needs to trouble shoot in the future?

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

No branches or pull requests

3 participants