----- Original Message -----
From: "Dan Callaghan" <dcallagh(a)redhat.com>
To: "beaker-devel" <beaker-devel(a)lists.fedorahosted.org>
Sent: Tuesday, January 6, 2015 1:17:54 PM
Subject: Re: [Beaker-devel] Running Beaker's tests in a Docker container
Excerpts from Amit Saha's message of 2015-01-05 10:02 +10:00:
> While working with beaker‘s code base, I often feel the need to run my
> tests for a patch/feature and continue to work on with different
> things while they run, including running other tests testing something
> different. Currently this is not possible since we start off with
> a clean database on every test run and simultaneous runs would
> obviously make one run step on another’s feet.
> I finally have an initial docker based prototype for making this
This is very neat.
It would be nice if this were included in the Misc/ directory with the
Could it also do an rpm build inside the container, and then install the
beaker-integration-tests package instead of running them from a copy of
a git checkout? That way we know the dependencies are right. You could
just re-use Misc/rpmbuild.sh. Build an SRPM outside the container, then
inside the container use yum-builddep and then build the SRPM.
Yeah, that is what I attempted at the first go, but I can't recall what was
the issue I ran into. I will reattempt it.
Could we upload a Docker image to the registry which has the base distro
plus all Beaker dependencies installed? Then we can avoid the first step
of build_base_image.sh. You could call the images
beaker-development-rhel-7. Can we register a namespace for Beaker on the
docker.io registry somehow?
I like the idea. I think we can just create an a/c with "beaker-project"
and then all our images will be beaker-project/image-name.
SED, Hosted & Shared Services
Red Hat, Inc.