-
Notifications
You must be signed in to change notification settings - Fork 481
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
Make DOCUMENTER_KEY decoding error more helpful #697
Labels
Comments
Closed
Finding this issue was a great help to me at least! |
Hi! I've found that error: https://travis-ci.org/diegozea/MIToS.jl/jobs/463040461 How can I solve it? |
I solved the problem in my package by generating a new key as described in https://juliadocs.github.io/Documenter.jl/stable/man/hosting/#SSH-Deploy-Keys-1 |
mortenpi
added a commit
that referenced
this issue
Dec 10, 2018
mortenpi
added a commit
that referenced
this issue
Dec 10, 2018
* Print a more helpful error if base64decode fails for the provided key. * Use SSH batch mode -- this means that SSH won't ask for passphrase and time out the Travis build if the SSH key is problematic. * Also, print a more helpful error if git fetch throws an error, most likely due to a key misconfiguration. Closes #697
mortenpi
added a commit
that referenced
this issue
Dec 10, 2018
* Print a more helpful error if base64decode fails for the provided key. * Use SSH batch mode -- this means that SSH won't ask for passphrase and time out the Travis build if the SSH key is problematic. * Also, print a more helpful error if git fetch throws an error, most likely due to a key misconfiguration. Closes #697
mortenpi
added a commit
that referenced
this issue
Dec 10, 2018
* Handle DOCUMENTER_KEY errors better in deploydocs * Print a more helpful error if base64decode fails for the provided key. * Use SSH batch mode -- this means that SSH won't ask for passphrase and time out the Travis build if the SSH key is problematic. * Also, print a more helpful error if git fetch throws an error, most likely due to a key misconfiguration. Close #697
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If there's something wrong with
DOCUMENTER_KEY
and Documenter can't decode it, the error is a bit cryptic, e.g.:The text was updated successfully, but these errors were encountered: