hybridgroup
Use a custom Docker container for builds
What
Run the Gobot build process inside a custom Docker container
Why
This will dramatically speed up the build process, as it will make use of Docker's container image layer cache to ensure that the system lib installation process effectively only has to happen once per active TravisCI Docker host instead of on every single build.
How
The process is outlined here:https://docs.travis-ci.com/user/docker/
Who?
I volunteer to do this if @deadprogram is down with it.
This seems like an extremely good idea. Probably should have done this a while ago, or at the very least I should have done that instead of switching to the Travis build cache for the recent changes to support GoCV and OpenCV 3.3.
Ok cool. I've put together a container locally and am figuring out how Travis works when you're using both a container and testing different versions of Go. Ideally it'd let me just install each supported version of Go myself in different tagged containers, b/c then I could move just about everything except for the test run and style vetting into the image, but I need to play around with it a bit.
Do you have a DockerHub account for Gobot?
PS I realized after I wrote this original ticket that the lengthy build time was still a lot shorter than every single thing getting installed from scratch. OpenCV is a beast... 😄
This was released as part of v1.8.0 thanks again for your awesome work, @trevrosen
This particular piece of the puzzle isn't 100% worked out yet so I'm going to re-open until I can put together the full container and have it leveraged in Travis.