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_TOKEN secure variable needs to be added to travis-ci #47

Closed
zbeekman opened this issue Jul 2, 2015 · 8 comments
Closed

GH_TOKEN secure variable needs to be added to travis-ci #47

zbeekman opened this issue Jul 2, 2015 · 8 comments

Comments

@zbeekman
Copy link
Contributor

zbeekman commented Jul 2, 2015

Hi Stefano, as I mentioned in #45, I think you still need to add a private/secure variable through the Travis-CI repository settings containing a working GH token. See #45 for instructions on how to do this. As you can see in the latest build the GH_TOKEN variable appears to be evaluating to the null string, preventing the deployment of the FORD documentation

@szaghi
Copy link
Owner

szaghi commented Jul 2, 2015

Sure, I forget to do...

@zbeekman
Copy link
Contributor Author

zbeekman commented Jul 2, 2015

Can you go to travis and resubmit the last build once you’ve added this, just so that we can make sure that everything is now working?

@szaghi
Copy link
Owner

szaghi commented Jul 3, 2015

Done, but the deploy seems to not work

@zbeekman
Copy link
Contributor Author

zbeekman commented Jul 4, 2015

I’ll take a look

@zbeekman
Copy link
Contributor Author

zbeekman commented Jul 6, 2015

It looks like you named your environment variable something other than GH_TOKEN: https://travis-ci.org/szaghi/FLAP/builds/69285565#L91

If you had named it GH_TOKEN you would have seen a line like this: https://travis-ci.org/zbeekman/json-fortran/jobs/69347547#L80

Please create secure variable who’s name matches exactly GH_TOKEN holding a github token with commit privileges. makedoc.sh can be modified if you like to use a variable name other than GH_TOKEN but please note that bash variables should not have spaces in their name, so your current variable name will never work.

@szaghi
Copy link
Owner

szaghi commented Jul 6, 2015

Opssss, I think you are rigth, sorry. Tomorrow I'll fix it! Thank you

@szaghi
Copy link
Owner

szaghi commented Jul 7, 2015

Done, thank you @zbeekman !

@szaghi szaghi closed this as completed Jul 7, 2015
@zbeekman
Copy link
Contributor Author

zbeekman commented Jul 7, 2015

No problem, thanks for such a cool project!

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

2 participants