Running Beaker on Windows about beaker HOT 9 CLOSED

Inclusion of 'fat binaries' starts with Nokogiri 1.6.2 https://github.com/sparklemotion/nokogiri/blob/master/CHANGELOG.rdoc#162--2014-05-12

from beaker.

@Aethylred you might be able to workaround for the time being by installing the ruby devkit from rubyinstaller.org. Make sure to select the compiler version that matches your ruby version.

from beaker.

I've tried that, to no avail. I've even installed the whole Windows and mingw development environment. I'm not a Ruby developer, having to install the dev kit to use a testing tool seems overkill.

(OTOH I've got things to say about packages that require compiler tools on Linux too)

from beaker.

beaker is only designed to be able to run tests on windows nodes, not to be run on windows itself - you are in pretty much uncharted territory here so I can't say if there is a way to get it to work.

from beaker.

I don't think designed is the word you want there, it's more that there was no intention for it to run under Windows... however without the operational environment for beaker being specified in the documentation it would be assumed that beaker can run where Ruby, Puppet and Vagrant can be run.

from beaker.

The more relevant point (that came to me later) is that if a policy ever comes in that module PR must include beaker acceptance tests (like they now require puppet-rspec tests), then this will exclude users who develop modules on Windows (i.e. me) unless some kind of hosted beaker test suite is provided (similar to Travis).

Note: though I contribute to Linux modules, the environment I develop in is Windows, because of stupid policy and compliance regulations we do our work in.

from beaker.

I've run into similar issues on x64 Windows. On that platform, Nokogiri requires a 1.6.x version to build properly, and our gemspec references ~> 1.5.10.

http://stackoverflow.com/a/23437057

I'm not sure what to make of the comment in the gemspec about the inclusion of this version for Ruby 1.8 support, but since we haven't shipped a Ruby 1.8 version on Windows any longer, my suggestion is to simply exclude Nokogiri from the gemspec on Windows.

https://github.com/puppetlabs/beaker/blob/master/beaker.gemspec#L51

Change

s.add_runtime_dependency 'nokogiri', '~> 1.5.10'

to

platform ||= RUBY_PLATFORM[/java/] || 'ruby'
s.add_runtime_dependency 'nokogiri', '~> 1.5.10' if platform.to_s == 'ruby'

You can see a more complete example of the use of platform specific dependencies here:
https://github.com/apache/buildr/blob/7760bcfb73afb59e7db5e4aaf35ee881aeec449f/buildr.gemspec

I don't have the cycles to verify this now @Aethylred , but perhaps you could build the gem locally and try to install it with those changes.

from beaker.

Last comment from @Iristyle quite a while back.

Please re-open if you need further help.

from beaker.

In case people get to this page when searching for a solution to install Beaker on Windows:

I was able to install beaker on Windows. For me, I installed current Ruby release (2.1.5) AND devkit and with those two, I was able to install beaker. So this issue appears to be at least resolved from that aspect.

from beaker.