Skip to content

r-devel @ Travis

6 messages · Peter Meissner, Gábor Csárdi, Måns Magnusson +1 more

#
Hi!

I'm developing R packages and use Travis CI for continous integration. When
submitting to CRAN Im suggestet to test the package using the latest
R-devel. I would like that all test where run using Travis. Is there anyone
who knows if this is possible to run travis test using the latest r-devel?
#
Hey,

Metacran's rbuilder is the place to get started:  
https://github.com/metacran/r-builder

You should be good to go by placing this in your Github repo (branch):  
https://github.com/metacran/r-builder/blob/master/.travis.yml

.. than tell Travis to whatch you repo.


Best, Peter




Am .01.2016, 09:45 Uhr, schrieb M?ns Magnusson <mons.magnusson at gmail.com>:

  
    
#
On Mon, Jan 18, 2016 at 9:00 AM, Peter Meissner
<retep.meissner at gmail.com> wrote:
Actually this file is for checking r-builder itself, which is somewhat special.

For a regular R package I think it is better to start with this one:
https://raw.githubusercontent.com/metacran/r-builder/master/sample.travis.yml

Don't forget to rename it to .travis.yml

Gabor

[...]
#
On 18 January 2016 at 09:45, M?ns Magnusson wrote:
| I'm developing R packages and use Travis CI for continous integration. When
| submitting to CRAN Im suggestet to test the package using the latest
| R-devel. I would like that all test where run using Travis. Is there anyone
| who knows if this is possible to run travis test using the latest r-devel?

Literally "anything is possible" subject to the constraint of Travis hosting
on Ubuntu 12.04 (aka "Precise") with an opt-in to Ubuntu 14.04 (aka "Trusty").

So anything you can build there, or build yourself somewhere else in order to
run there -- and I have made the case that the Launchpad build system by
Canonical/Ubuntu is good -- will work.

12.04 / 14.04 are sometimes a little restrictive, but one can generally do
just fine.  Now, I (as the one rolling up the r-release .deb packages for R)
never created one for R-devel -- but Gabor filled that gap for purposes of
r-builder / r-hub.  That is your (current) best bet.

For what it is worth, I still prefer my R-devel tests to be local -- but use
in Travis is a perfectly fine approach.

Cheers, Dirk
#
Thank you all for the comments and suggestions!

I got the link from Garbor to work, but that is the old r-travis approach
(using C). I tried the same approach with native R Travis build but
unfortunately it did not work. So I contacted Jim Hester and he told me
that they are now actively working with implementing multiple R versions in
the native R builds.

/M?ns

2016-01-18 15:17 GMT+01:00 Dirk Eddelbuettel <edd at debian.org>:

  
    
#
On 18 January 2016 at 17:38, M?ns Magnusson wrote:
| I got the link from Garbor to work, but that is the old r-travis approach
| (using C).

I prefer that approach. It works _now_ and you get complete control. 

| I tried the same approach with native R Travis build but
| unfortunately it did not work. So I contacted Jim Hester and he told me that
| they are now actively working with implementing multiple R versions in the
| native R builds.

Ahh, the good old 'that will be fixed in the next version' trick. You'd
almost suspect Jim now works for a software company ;-)

Dirk