On 01/10/14 15:27, Trevor Vaughan wrote:
> How does running tests with SELinux contexts work in a Docker instance?
> (I'm not guessing very well, but it would be nice to have confirmation).
I think the way it works recently (since Dan Walsh's work around Docker
0.10/11) is that /sys/fs/selinux is
> Ah ok, yeah I was talking mainly about module testing. But yeah, the general
> gist is if you want to run beaker tests for free and in a public CI, Werker
> + Docker seems to work :)
Yeah absolutely, it's an exciting way of doing tests really. There are
some exceptions of course - for example if
How does running tests with SELinux contexts work in a Docker instance?
(I'm not guessing very well, but it would be nice to have confirmation).
Thanks,
Trevor
On Wed, Oct 1, 2014 at 10:15 AM, Peter M Souter wrote:
>
>> Actually, we generally use VSphere now (I presume you mean just module
>>
>
>
> Actually, we generally use VSphere now (I presume you mean just module
> testing), just FYI. We also have a small smattering of EC2 for other
> projects, but most of our stuff is VSphere afaik.
>
> ken.
>
Ah ok, yeah I was talking mainly about module testing. But yeah, the
general gist
> I know PuppetLabs themselves use their own Jenkins server with Virtualbox on
> it, but for those who want to get beaker stuff up publicly easily and (for
> now, free) wercker seems to work pretty well! :)
Actually, we generally use VSphere now (I presume you mean just module
testing), just FYI.
Hi all!
So I saw Gareth's talk on Continuously testing infrastructure talk at
Puppetconf, I saw that wercker has docker support.
I'd seen a few people hack together docker support in Travis, but it was a
bit hacky (https://github.com/lukecyca/travis-docker-example) and whilst
there seems to b
