{"id":1786,"date":"2013-06-11T10:51:19","date_gmt":"2013-06-11T15:51:19","guid":{"rendered":"http:\/\/www.kickflop.net\/blog\/?p=1786"},"modified":"2013-06-27T20:09:31","modified_gmt":"2013-06-28T01:09:31","slug":"jenkins-running-test-kitchen-via-vagrant-on-windows","status":"publish","type":"post","link":"https:\/\/www.kickflop.net\/blog\/2013\/06\/11\/jenkins-running-test-kitchen-via-vagrant-on-windows\/","title":{"rendered":"Jenkins running Test-Kitchen via Vagrant. On Windows."},"content":{"rendered":"

If you’re like me and for various reasons (we’ll not discuss) the physical hardware you have access to right now must run Windows, you might think you’re out of luck as far as getting Jenkins running Test-Kitchen jobs as Joshua Timberman shows in Test Kitchen and Jenkins1<\/a><\/sup>. But there’s hope if you have patience. I’ll show how I got it working, and I’m looking forward to ideas from you on how to develop better solutions to some of the kludges. There’s not much original material here, but instead of mentioning just my piece of things and linking you coldly to 2 other places for the rest of the info, I figured I would write up as much of the whole experience as I felt up to.<\/p>\n

Prerequisites<\/h2>\n

Windows Add-Ons<\/h3>\n

It is assumed that you have the following installed. If not, do so.<\/p>\n

    \n
  1. Ruby 1.9.3 from rubyinstallers.org<\/a><\/li>\n
  2. Git 1.8.x for Windows from git-scm.com\/download<\/a>. All commands shown below are run under a “Git Bash” session and not Windows’ cmd.exe!<\/strong> unless explicitly stated as such.<\/li>\n
  3. Jenkins\n<\/ol>\n

    Ruby Gems<\/h3>\n

    At this point, you should open a Git-Bash shell and ensure that which gem<\/code> indicates the one found in the Ruby 1.9.3 install you did previously. For me, that was \/c\/Ruby193\/bin\/gem<\/code>.<\/p>\n

    Start with: gem install bundler<\/code><\/p>\n

    Then, in the directory containing the cookbook you want to test, create a Gemfile<\/code> with the following contents:<\/p>\n

    \r\nsource 'https:\/\/rubygems.org'\r\ngem 'test-kitchen', '~> 1.0.0.alpha.7'\r\n<\/pre>\n
    Run: bundle install<\/code><\/p>\n
    Run: kitchen init<\/code><\/p>\n
    Run: bundle install<\/code> (yes, again)<\/p>\n
    Run: kitchen help<\/code> to ensure Test Kitchen can at least run.<\/p>\n
    Edit .kitchen.yml<\/code> to look like the following (configure later how you want):<\/p>\n
    \r\n---\r\ndriver_plugin: vagrant\r\ndriver_config:\r\n  require_chef_omnibus: true\r\n\r\nplatforms:\r\n- name: ubuntu-12.04\r\n  driver_config:\r\n    box: opscode-ubuntu-12.04\r\n    box_url: https:\/\/opscode-vm.s3.amazonaws.com\/vagrant\/opscode_ubuntu-12.04_provisionerless.box\r\n\r\nsuites:\r\n- name: default\r\n  run_list: []\r\n  attributes: {}\r\n<\/pre>\n
    At this point you should be able to run kitchen test<\/code> and see something success-like.<\/p>\n
    Jenkins<\/h3>\n
    The Windows installer for Jenkins is nice in that it configures Jenkins to run as a Windows service. So go get and install that from jenkins-ci.org\/windows\/latest<\/a>. Once installed, you should be able to hit http:\/\/localhost:8080<\/code> and see the Jenkins web UI.<\/p>\n
    Use the web UI to install the “Git” plugin.<\/p>\n
    Configure a new Jenkins job. For my case, it looked like the following.<\/p>\n