I'm dreaming of a (hosted) RStudio CI/CD

[cole]

As far as packages and CI / CD are concerned, I think some valuable thoughts / discussion can be had in these topics:

How do you test your internal packages (Travis, Jenkins, by hand?)

As an R user developing an internal package, what tools do you use for automated testing. Do you have access to continuous integration software like Jenkins and Travis? Would it be helpful if RStudio Package Manager ran automated tests? Do you use something else?

What is next for RStudio Package Manager? What should be next?

RStudio just released the public beta of the RStudio Package Manager. What's up next? On the short term horizon, we’re working on two exciting features: The ability to version repositories and “freeze” them. You may have noticed that in RStudio Package Manager a repository URL includes “/latest”. RStudio Package Manager automatically versions every change to a repository with a unique ID that can be used in place of “latest”. In the next release, we’ll provide users access to these IDs so that in certain contexts they can install packages from a “frozen” repository. For example, the following line in a Dockerfile would be guaranteed to always return the same packages when the container is…

I think the latter makes a point about when would you clone the git repository / kick things off? Would you be looking for a Git hook that you control, or would you be looking for a service that would be watching the Git repo for tags / commits on a certain branch to trigger a build? You also might think about a timeline - maybe kick off a build / test every week even if no commits have made it to master?