Beaker-extensions

[Peter M Souter]

Hi All!

So, Beaker is awesome. But there are some features that are nice-to-haves that aren't needed for Puppetlabs themselves:

https://github.com/puppetlabs/beaker/issues/512

https://github.com/puppetlabs/beaker/issues/499

So, I thought about having these as extensions in a separate gem, that if someone wants to run tests in their module for FreeBSD, or run it against new providers such as DigitalOcean, Linode etc. they can add them.

When this gets into a workable state, I'd like to move it to https://github.com/puppet-community :)

I'm not a Ruby whiz, but this is what I've come up with so far:

https://github.com/petems/beaker-extensions

I was planning on working on this for #puppethack, any help is appreciated! :D

Thanks

Regards

[Spencer Krum]

I think this is a good idea. It is a bit concerning that Alice doesn't think there is a good way to add extensions to beaker right now, maybe development time at #puppethack could be spent shoring that up. I'm +1 on this and would add my limited experience to the maintainer hat pool.

 

--

Spencer Krum

ni...@spencerkrum.com

 

--

You received this message because you are subscribed to the Google Groups "Puppet Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/8c740faf-c45f-41fa-91a1-8d6f3dd722d7%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

 

[Liam Bennett]

I have to +1 this as well. I think it is hugely important to work out an extension mechanism if only so that we can eventually break up the codebase and have them managed separately.

I am pretty familiar with the code at this point so I am happy to get involved, either directly on the current extension you're working on or on fixing any nasty bits beaker.

[Justin Stoller]

I've been working with the module team here and have been looking at helping out with some of the features we need (pluggable hypervisors, improved Vagrant support, improved Windows support, better RSpec formatting...). I was trying to figure what things I'd work on during #puppethack, but if there's going to be some folks focusing on Beaker I'll definitely join you guys!

See you on Thursday. I'm justinstoller on Github and Freenode

 - Justin

On Fri, Nov 28, 2014 at 1:21 PM, Liam Bennett <liam.j....@gmail.com> wrote:

I have to +1 this as well. I think it is hugely important to work out an extension mechanism if only so that we can eventually break up the codebase and have them managed separately.

I am pretty familiar with the code at this point so I am happy to get involved, either directly on the current extension you're working on or on fixing any nasty bits beaker.

--
You received this message because you are subscribed to the Google Groups "Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/32c74a82-fbb3-4a6f-a7d9-13ccc9fccc0e%40googlegroups.com.

[Daniele Sluijters]

Hi,

I would be interested to help out here too. We need things like a custom provider for our own cloudy thing at Spotify and a few other extension points so that we can move away from rspec-system-puppet .

[Hunter Haugen]

I commented on https://github.com/puppetlabs/beaker/issues/499 with my method for adding a custom (closed sourced; boo) hypervisor for testing in one module. The exact same mechanism could be used for all manner of extension gems (or one gem, as beaker-extensions is).

beaker-rspec is essentially an extension gem also. It extends beaker with the rspec dsl, and also serverspec (which I haven't had time to update for serverspec 2.0 yet).

-Hunter

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/921f9146-57d8-404b-88e9-bc80d343ae52%40googlegroups.com.