On 26 July 2018 at 01:36, Tom Kent via Boost
On Wed, Jul 25, 2018 at 4:17 AM, Mateusz Loskot via Boost
wrote: Boost - Dev mailing list wrote
On Tue, May 8, 2018 at 6:59 AM, James E. King, III via Boost
wrote: I submitted a pull request into the superproject containing some docker scripts. The intention of this is to simplify managing a docker build environment for boost:
https://github.com/boostorg/boost/pull/184
[...] This partially came out of the discussion we had a number of months back about how we handle third party dependencies. For the most part one has to look at README files in various locations to learn about them. This is an attempt to pull all the dependencies together for a complete build into one place (the Dockerfile).
I just wanted to mention that I've got a stable of boost docker images available at: https://hub.docker.com/r/teeks99/boost-cpp-docker/
built from the git repo: https://github.com/teeks99/boost-cpp-docker
I initially created these as the source for the linux regression runners that I manage (teeks99-02*, teeks99-03*)
Tom,
Do you also automated running the regression tests?
Could you explain your workflow with those docker images you perform to run the complete Boost regression tests suite?
[...] As far as how I use them in the regression tests, I've got a bit of tooling setup here: https://github.com/teeks99/boost-build/tree/master/Regression
It is mostly just a couple python scripts that continuously cycle between configurations and the lists of configs that I want to run on each machine, windows and linux.
This looks like something I've been looking for/thinking of. I'm going to try it out in action soonish. Thanks for sharing. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net