Travis-CI (or similar) for Test-Kitchen, anyone?

Ohai!

I would love to see something like travis-ci for testing cookbooks via
test-kitchen.

In fact I tried to get an LXC container up an running on travis-ci but that
doesn't seem to work:

Not everybody runs an in-house Jenkins server for testing his cookbooks,
and even if so the builds are not publicly visible (think of test-kitchen
build badges).

I firmly believe that the quality of existing (i.e. non-opscode) cookbooks
would considerably benefit from that, if something like travis-ci for
cookbooks would exist.

Anyone working on / interested in that?

Cheers,
Torben

Certainly interested. I know my coworker was putting something together on
this (via EC2) but it is on indefinite hold for now.

On Tue, Aug 6, 2013 at 1:45 PM, Torben Knerr ukio@gmx.de wrote:

Ohai!

I would love to see something like travis-ci for testing cookbooks via
test-kitchen.

In fact I tried to get an LXC container up an running on travis-ci but
that doesn't seem to work:
Trying to run LXC containers on travis-ci · Issue #1273 · travis-ci/travis-ci · GitHub

Not everybody runs an in-house Jenkins server for testing his cookbooks,
and even if so the builds are not publicly visible (think of test-kitchen
build badges).

I firmly believe that the quality of existing (i.e. non-opscode) cookbooks
would considerably benefit from that, if something like travis-ci for
cookbooks would exist.

Anyone working on / interested in that?

Cheers,
Torben

Sounds interesting!

Btw: @Opscode willing to sponsor such efforts? :slight_smile:

On Tue, Aug 6, 2013 at 8:05 PM, Andrew Gross andrew@yipit.com wrote:

Certainly interested. I know my coworker was putting something together
on this (via EC2) but it is on indefinite hold for now.

On Tue, Aug 6, 2013 at 1:45 PM, Torben Knerr ukio@gmx.de wrote:

Ohai!

I would love to see something like travis-ci for testing cookbooks via
test-kitchen.

In fact I tried to get an LXC container up an running on travis-ci but
that doesn't seem to work:
Trying to run LXC containers on travis-ci · Issue #1273 · travis-ci/travis-ci · GitHub

Not everybody runs an in-house Jenkins server for testing his cookbooks,
and even if so the builds are not publicly visible (think of test-kitchen
build badges).

I firmly believe that the quality of existing (i.e. non-opscode)
cookbooks would considerably benefit from that, if something like travis-ci
for cookbooks would exist.

Anyone working on / interested in that?

Cheers,
Torben

i doubt we'll be able to run lxc ever on openvz. openvz was trying to get
merged on mainline kernel before the rise of chgroup. container
implementation on openvz and lxc is significantly different,

i'll be taking a stab at it, but i doubt how much i'll be able to reuse
test-kitchen though. I am planning to use vinalla schroot/chroot along with
debootstrap

On Tue, Aug 6, 2013 at 10:45 AM, Torben Knerr ukio@gmx.de wrote:

Ohai!

I would love to see something like travis-ci for testing cookbooks via
test-kitchen.

In fact I tried to get an LXC container up an running on travis-ci but
that doesn't seem to work:
Trying to run LXC containers on travis-ci · Issue #1273 · travis-ci/travis-ci · GitHub

Not everybody runs an in-house Jenkins server for testing his cookbooks,
and even if so the builds are not publicly visible (think of test-kitchen
build badges).

I firmly believe that the quality of existing (i.e. non-opscode) cookbooks
would considerably benefit from that, if something like travis-ci for
cookbooks would exist.

Anyone working on / interested in that?

Cheers,
Torben

Can you run openvz containers inside openvz? Thinking of an openvz driver
for test-kitchen...

On Tue, Aug 6, 2013 at 8:13 PM, Ranjib Dey dey.ranjib@gmail.com wrote:

i doubt we'll be able to run lxc ever on openvz. openvz was trying to get
merged on mainline kernel before the rise of chgroup. container
implementation on openvz and lxc is significantly different,

i'll be taking a stab at it, but i doubt how much i'll be able to reuse
test-kitchen though. I am planning to use vinalla schroot/chroot along with
debootstrap

On Tue, Aug 6, 2013 at 10:45 AM, Torben Knerr ukio@gmx.de wrote:

Ohai!

I would love to see something like travis-ci for testing cookbooks via
test-kitchen.

In fact I tried to get an LXC container up an running on travis-ci but
that doesn't seem to work:
Trying to run LXC containers on travis-ci · Issue #1273 · travis-ci/travis-ci · GitHub

Not everybody runs an in-house Jenkins server for testing his cookbooks,
and even if so the builds are not publicly visible (think of test-kitchen
build badges).

I firmly believe that the quality of existing (i.e. non-opscode)
cookbooks would considerably benefit from that, if something like travis-ci
for cookbooks would exist.

Anyone working on / interested in that?

Cheers,
Torben

I'm working on something like this but it doesn't use test-kitchen.
Badging is an important part of the equation. I'll see about
open-sourcing it once I'm done ... I've already got something in the
open-source-contribution pipeline and I'm waiting to see how long that
takes to make it out before I start putting more things through it.

On Tue, Aug 6, 2013 at 11:19 AM, Torben Knerr ukio@gmx.de wrote:

Can you run openvz containers inside openvz? Thinking of an openvz driver
for test-kitchen...

On Tue, Aug 6, 2013 at 8:13 PM, Ranjib Dey dey.ranjib@gmail.com wrote:

i doubt we'll be able to run lxc ever on openvz. openvz was trying to get
merged on mainline kernel before the rise of chgroup. container
implementation on openvz and lxc is significantly different,

i'll be taking a stab at it, but i doubt how much i'll be able to reuse
test-kitchen though. I am planning to use vinalla schroot/chroot along with
debootstrap

On Tue, Aug 6, 2013 at 10:45 AM, Torben Knerr ukio@gmx.de wrote:

Ohai!

I would love to see something like travis-ci for testing cookbooks via
test-kitchen.

In fact I tried to get an LXC container up an running on travis-ci but
that doesn't seem to work:
Trying to run LXC containers on travis-ci · Issue #1273 · travis-ci/travis-ci · GitHub

Not everybody runs an in-house Jenkins server for testing his cookbooks,
and even if so the builds are not publicly visible (think of test-kitchen
build badges).

I firmly believe that the quality of existing (i.e. non-opscode)
cookbooks would considerably benefit from that, if something like travis-ci
for cookbooks would exist.

Anyone working on / interested in that?

Cheers,
Torben