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
tic::use_tic() for automatic deployment of pkgdown and testing on AppVeyor #28
Comments
Thanks for re-inviting me, unfortunately I still can't access the Travis and GitHub configuration from this repository. With the most recent version of {tic}, you can now do: tic::use_tic(wizard = FALSE, linux = "travis", mac = "none", windows =
"appveyor", deploy = "travis", matrix = "travis") to either get a quick error, or succeed. I forgot to mention that you probably also need a GitHub token, create with This is a one-off exercise that hopefully will make things easier in the longer run. Thanks for your help! |
OK I've done the |
Hmm there is a build failure – it is unable to install tic at the start of the travis job. https://travis-ci.org/jefferislab/RANN/builds/631589524 I have switched the repo to my lab GitHub org (jefferislab) and made you an admin. Perhaps you might be able to debug? The build failure is still there: https://travis-ci.org/jefferislab/RANN/jobs/631596529 I'm not sure if there could be a PAT issue. |
I generated a new PAT (with identical scope) and it looks like the build is running ok now. In any case, I hope you can go ahead and make the changes you would like. |
Thanks, looks good. Do you want to test on AppVeyor too? The configuration has been created, I think you need to register the project with AppVeyor. I have changed the documentation source to the |
Could you please install
and run
If asked to overwrite
.travis.yml
, select "yes". You may need to set up a Travis access token withtravis::browse_travis_token()
.Benefits:
I can also do it if you increase my permissions to this repository.
I just noticed {RANN.L1} has been orphaned on CRAN, I'd like to update.
The text was updated successfully, but these errors were encountered: