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

[maxheld83]

thanks so much @MarkeD for taking the to time reply. Also a huge fan of all your cloudyr work and your thoughtful comments on the related thread –– very helpful.

@MarkeD

my workflow is 1) Start a project 2) Get it working locally in my local environment 3) run containerit on the file 4) commit it all to GitHub 5) Go for coffee whilst first Docker image builds on Build Triggers (now Cloud Build) 6) Deploy to X (presently Kubernetes)

I like to commit (with CI/CD) early and often, and am wondering how that might work. Have you developed your analyses from inside a Docker container running locally (or on GCE, FWIW)?
That would mean that whenever (system) dependencies change, I would (strictly speaking) have to rebuild from the Dockerfile, right?
containerit seems very awesome.

@MarkeD

you could pin the package version in your Dockerfile but I don't usually bother with that even as each build of the Dockerfile creates an image with a unique label (don't rely on latest tag), and that is my version control. So say I need to rely on dplyr 0.6 and code will break on dplyr 0.7 I will make sure to call the Docker image that was built at that time, which is preserved as an image/tag on Container images. (The Dockerfile is being built on every GitHub push)

I think I'd go for pinning the package version, or perhaps even using MRAN. I like everything to be reproducible just from the repo, with no other artefacts (container images).

@MarkeD

I also think RStudio is also working more with container support in the nightly builds from what I heard.

Can't wait to hear more about that.