Build not triggered after pushing to GitHub

[juliohm]

This happened in the past, but I don't understand what is the cause now, I have pushed various commits this week to my package and the documentation was not updated:

https://github.com/juliohm/ImageQuilting.jl

Can you please help me understand what is happening?

[mortenpi]

Documenter is skipping the deployment for some reason. Could you please set DOCUMENTER_DEBUG environment variable to true on Travis and re-run the latest linux 0.5 build?

[juliohm]

The only difference I remember now is that I used GitHub Releases and Attobot to trigger the build and the pull request to METADATA. It shouldn't be an issue though.

I added the environment variable DOCUMENTER_DEBUG with the value true and restarted the build.

[mortenpi]

Ah, you're using the old GITHUB_API_KEY method to give Documenter access to the repo. That was deprecated a while back (not fine grained enough) and was removed completely on Jan 29. You need to set up a new SSH key. There's more info here: https://juliadocs.github.io/Documenter.jl/stable/man/hosting.html#SSH-Deploy-Keys-1

Once that's working you should probably also remove the old token from you list access tokens.

[juliohm]

So the short key generated by Travis.genkeys is just the number in the middle after ssh-rsa and before the user@hostname markers, correct?

[juliohm]

Nevermind, GitHub asks for the whole thing. Moving with the process...

[juliohm]

Now I am getting an unrelated build error, I will report it in SimpleTraits.jl: https://travis-ci.org/juliohm/ImageQuilting.jl/jobs/200428164

[juliohm]

Problem solved, thank you @mortenpi. Can you please confirm I can delete the GITHUB_API_KEY from my GitHub account? The new Documenter.jl only uses the DOCUMENTER_KEY variable, correct?

[mortenpi]

Good to hear! Yes, you can remove GITHUB_API_KEY and you should probably remove the corresponding token from GitHub as well. Can be done on the access tokens page I think.

[juliohm]

Thanks, doing it :)

…

On Feb 13, 2017 11:06 AM, "Morten Piibeleht" ***@***.***> wrote: Good to hear! Yes, you can remove GITHUB_API_KEY and you should probably remove the corresponding token from GitHub as well. Can be done on the access tokens page <https://github.com/settings/tokens> I think. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#427 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADMLbZsZplaqvSQp7RttopLpl8swR-8Fks5rcKk5gaJpZM4L-E1b> .