Hexo should return a non-zero exit code if any error occurred in the generate progress.

[hv0905]

Check List

Please check followings before submitting a new feature request.

• [x] I have already read Docs page
• [x] I have already searched existing issues

Feature Request

I've just use a automatic pipeline for building and deploying my blog.

One day I finish my writing and make a git push. However, the build stage failed because of a random network/npm error:

Although this was a minor error that could have been resolved through a retry, the issue was exacerbated by the fact that the command hexo g exited with an exit code of 0. Consequently, the pipeline worker assumed that the build had succeeded, leading to the omission of a warning email to my mailbox.

To make the thing even worse, the deploy job is just after the build job, so the worker copied all the buggy file to my production environment and broke my production environment.

I hope hexo can exit with a non-zero code when some error occurred, so the deployment job can be cancelled, and warning mail by ci can be sent.

Others

[stevenjoezhang]

You can try to override hexo.log.error function, to make it terminate the process with non-zero exit code.

[hv0905]

You can try to override hexo.log.error function, to make it terminate the process with non-zero exit code.

What about adding a switch (such as --strict) to terminate the process whenever an error log was printed?