Hi, all;
   Over at the httpd project we've had some chats [1] about improving
our testing and moving towards a more CI type of model. Jacob has taken
the task of getting things initially set up with build bot
(bb_slave6_ubuntu AFAICT) and I was thinking further about how we can
improve the testing by using docker for running the test suite against
various Linux distributions. I cannot seem to locate documentation about
what software is available and installed on the slaves, but did stumble
across a puppet manifest that looks like it belongs to the slaves [2].
There's mention of a docker user group, but I don't see where the
docker-engine packages are installed. Would it be possible to enable use
of docker on the build slave(s)?

   I'm not a puppet expert (I use Chef, so bear with me), but it looks
like adding docker-engine to data/nodes/bb-slave6.apache.org.yaml will
get it installed. I'm unsure of where the appropriate place to configure
it would be (guessing in modules/buildbot_slave/manifests/buildbot.pp
with a conditional on whether docker-engine is in $slave_packges). There
may be no additional configuration required since
modules/build_slaves/manifests/jenkins.pp already puts jenkins user in
the docker group assuming the buildbot runs everything as the jenkins user.

   Does this sound doable? I know that disk space can be a sticking
point holding onto the docker images, but that can be managed by
removing intermediate containers and cleaning up any created
images/containers when the test suite is done.

[1]
https://lists.apache.org/thread.html/241369888e5aa7ccb8a77ddddddde3eb9940dfdcac80e0caf9777233@%3Cdev.httpd.apache.org%3E
[2]
https://git1-us-west.apache.org/repos/asf?p=infrastructure-puppet.git;a=blob;f=modules/build_slaves/manifests/jenkins.pp;h=4fce851b27ee77d70aefedb613c3833fb29503e1;hb=HEAD

-- 
Daniel Ruggeri

Reply via email to