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

gh-pages did not update #11

Open
timbl opened this issue Apr 5, 2016 · 1 comment
Open

gh-pages did not update #11

timbl opened this issue Apr 5, 2016 · 1 comment

Comments

@timbl
Copy link
Member

timbl commented Apr 5, 2016

For example
http://linkeddata.github.io/tabulator/js/panes/common/icons/noun_15177.svg
does not exist even though
https://github.com/linkeddata/tabulator/blob/gh-pages/js/panes/common/icons/noun_15177.svg
does.

The following mail form support@github.com

The page build failed with the following error:

Page build failed. For more information, see https://help.github.com/articles/troubleshooting-github-pages-build-failures.

GitHub Pages was recently upgraded to Jekyll 3.0. It may help to confirm you're using the correct dependencies:

 https://github.com/blog/2100-github-pages-now-faster-and-simpler-with-jekyll-3-0

If you have any questions you can contact us by replying to this email.
@timbl timbl changed the title hg-pages did not update gh-pages did not update Apr 5, 2016
@timbl
Copy link
Member Author

timbl commented Apr 5, 2016

Got a response to the last time, I now find:
Hi Tim,

Sorry about the generic error message. The full build logs are not available to users, but that is something we'd like to improve in the future.

It seems that the better-simple-slideshow submodule points to a commit that is no longer available in the "leemark/better-simple-slideshow" repository on GitHub. In our logs the error looks like this:

Unable to checkout '9d4365b029fa0ff761de08ed26adcf21716b16e9' in submodule path 'js/panes/slideshow/better-simple-slideshow'

You should be able to reproduce the error by running "git submodule update --init" in a fresh clone of the repository. Updating that submodule to a commit that the build process can fetch will fix the build failure.

We have a help guide on replicating our Jekyll builds[1], but since you aren't using Jekyll you may want to turn it off entirely by adding an empty file named ".nojekyll" to the root directory in the gh-pages branch. A .nojekyll file wouldn't have prevented this build failure, but it may help you avoid them in the future.

Let us know if you have any other questions.

Best regards,
John

1: https://help.github.com/articles/setting-up-your-github-pages-site-locally-with-jekyll/

“Page build failed” is not a very precise error message, and
the list at https://help.github.com/articles/troubleshooting-github-pages-build-failures is very general.

All I need is the files checked out with git submodules. I don’t use Jekyll

Can I get the logs from the gh-pages build?

Can I run some sort of validator or simmulate what you do?

timbl

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

No branches or pull requests

1 participant