Processed in order, so entries can depend on dependencies in a previous list.īrew_packages: A list of packages to install via brew. Installed before building and testing your package. travis.yml entries in these lists will be
However for rare cases the following fieldsĮach of the names below is a list of packages you can optionally specify as a Useful, for example, to deploy only from release via on: condition: "$TRAVIS_R_VERSION_STRING = release".įor most packages you should not need to specify any additional dependencies in TRAVIS_R_VERSION_STRING set to the string provided to r:, i.e.R_LIBS_SITE=/usr/local/lib/R/site-library:/usr/lib/R/site-library.TRAVIS_R_VERSION=3.2.4 Set to version chosen by r.R-Travis sets the following additional environment variables from the Travis Useful to test if the package builds on a vanilla macOS disable_homebrew: if true this removes the preinstalled homebrew.If your vignettes require additional TexLive packages youĬan install them using tlmgr install in the before_install step. The included TexLive distribution contains only a limited set of default Most of the time you should not need to specify any additional dependencies in
Information on using development remotes in your package. You can includeĭependencies on packages in development by listing them in the Remotes: field Package’s DESCRIPTION file, and install them from CRAN. Dependencies #īy default, Travis CI will find all R packages listed as dependencies in your The exact R version used for each build is included in the ‘R session information’įold within the build log. release) as opposed to the concrete version number (i.e 3.2.1) with the environmental variable TRAVIS_R_VERSION_STRING. You can access the above “channel” string (i.e. Language : r r : - oldrel - release - develĪs new minor versions are released, aliases will float and point to the most Improve this page on GitHub Building an R Project The README in our Git repository explains how to contribute.
0 kommentar(er)
