At rOpenSci, we encourage R package developers to take advantage of Continuous Integration services to automatically check the package on different platforms, with different versions of R. The rOpenSci dev guide dedicates chapter 2 to the topic of Continuous Integration Best Practices, and recommends a few common CI vendors, including Travis CI.
@jeroenooms What would your current recommendations be for or against travis? You state in your original blog post:
It is still unclear what exactly the new [travis] product will look like, perhaps it can still be useful
Any updated recommendations? In particular, any suggestions for or against rOpenSci as an organisation accepting peer review submissions which use travis for CI?
You should no longer be using Travis. The R language in travis is unmaintained since both of the maintainers (Jim and me) are no longer maintaining it after they terminated the open source tier.
Also we are no longer updating the R installers for travis, and soon the old ones will be deleted as well, so at that point things will completely stop working.