Leaving travis for docker – will I get my life back?

[maxheld83]

I anyone is still interested, I did decide to leave travis for Docker, and I have gotten part of my life back .

This process has been made a lot easier and more appealing by the recently announced GitHub actions, which allows you to run arbitrary Docker containers as a CI/CD of sorts directly on GitHub.

This by no means solves all of the limitations of Docker mentioned by @cole, but has greatly reduced the friction around using Docker, and thus made it yet more appealing.

I now develop inside the same container that I also use for CI/CD on GitHub actions, which is awesome. No more duplicate environment provisioning. (Of course, many of the caveats remain: Docker images are reproducible, but not Dockerfiles per se).

Anyway, I went ahead and filled the gaping whole left in my life by no longer wrestling with TravisCI by developing some GitHub actions for R and an accompanying package:

GitHub actions for R

Announcement here:

GitHub Actions for R: Introducing the ghactions package

GitHub actions are a new workflow automation feature of the popular code repository host GitHub. The product is currently in limited beta . Among many other things, it allows you to run (pretty much arbitrary) Continuous Integration / Continuous Delivery (CI/CD) workflows. Sort of like TravisCI, but arguably way more flexible. I got into the limited beta while back and have been using it for a couple of weeks now. I think it's pretty amazing, and it may have some potential for R users. A gif says is best: [pkgwf] (This is a complete package build/check/doc/deploy workflow). To benefit from all the inherent flexibility, GitHub actions is arguably best used via GitHub's own visual edit…