GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Thanks, but I'm using https://github.com/craigcitro/r-travis for other projects. Would you mind using that instead?
Thank you. I wasn't aware of the other R-Travis. Currently, my version has some advantages:
Craig's version has the advantage of already being familiar to me, and he's planning on submitting it to travis to add an official R backend. I'd really like to see everyone standardising on one approach.
I think this is a good compromise -- testing is enabled when the branch has suffix -ci.
I think that's a reasonable compromise. Please squash and I'll merge. (Also, if you're going to bump the version in description, please also add a heading the news)
Note how this PR doesn't show the Travis build state anymore, just because it hasn't been built on Travis. See e.g. yihui/knitr#642 for comparison. Do you really want to abandon this feature?
Ok, that's a bummer. Let's flip and explicitly opt out - how about using the suffix -expt (i.e. for experimental) to opt out of automatic builds.
Done. As of today, the builds seem to err when trying to install r-base-dev: https://travis-ci.org/krlmlr/plyr/builds . This doesn't happen with knitr builds: https://travis-ci.org/krlmlr/knitr/builds .
enable continuous integration via craigcitro/r-travis
- ignore .Rhistory file created by RStudio
- bump version, add heading for new version number
Build passes again after recent changes to r-travis.
don't restrict tests only to master branch; instead test all branches…
… that don't end with -expt
I guess I did this by hand? Please resubmit if you think you could improve the existing config.