-
Notifications
You must be signed in to change notification settings - Fork 190
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
Travis-CI support #22
Comments
See https://github.com/mozilla/oghliner which allows you to easily configure auto-deploy from Travis-CI. |
@MoOx a PR adding It looks like there is also an issue with these silent failures. I'll try to find some time to dig into it. |
Yep I also get silent failures, rm -rf node_modules seems to work but that would be awesome to know why its failing |
Otherwise it silently fail sometimes: not good tschaub/gh-pages#22 (comment)
I'll call this fixed with #23. Please reopen if this is not enough. |
always handle error argument in a callback
Working for me with the --repo. Thanks! |
@tschaub The suggested fix does not seem to be working for me with Travis. The error I get is:
It's running this task:
The GH_TOKEN should be working correctly as it worked fine with another deploy task. I'd set the user from the command line but did not find a command to do so with |
@ismay did you try to do what is asked? Example https://github.com/MoOx/statinamic/blob/c2ad13a7e459aaadf3138be3717ca5394c57/docs/scripts/deploy.sh#L3-L7 Some modules does this with random email/name. |
@MoOx I did, in fact that's how I used to do it. But I thought that there might be a gh-pages specific way to deal with this, since there wasn't any mention of setting these values manually in this issue. |
it would be nice if this would stub those |
You could also use Travis GitHub Pages Deployment, only using |
I tried to use this module to autodeploy from Travis-CI.
From the build log it seems to work https://travis-ci.org/MoOx/statinamic/builds/81526747#L639-L647
but it doesn't push anything.
FYI, I configured a GH_TOKEN value, I guess you are not using it, but why is the log saying it's working?
Are you open to a PR to handle this?
The text was updated successfully, but these errors were encountered: