Currently we are on a Legacy Dyno which prevents us from using the Pipelines feature of Heroku which lets us super easily spin up a version of the app for each PR. Moving to a modern dyno will net us a few other benefits like SSL and better perf to boot.

Moving issue to docs - test-kitchen/kitchen-vagrant#149

Basically for Windows folks it'd be good to mention that if you get an error like that you should check your $PATH

The front page of kitchen.ci still advises you to install Test Kitchen via a gem install -- this is unnecessary since it's bundled with ChefDK, so we should mention that as the preferred option.

Moving from test-kitchen/test-kitchen#1440 for @darkn3rd

Shell provisioner has no documentation. I had to look at unit tests and source code to elicit the options for shell provisioner. Currently, there's no documentation that documents the features available for the shell provisioner, other than the source code.

Non-programmer users may likely be intimidated to dive to this level to figure out how to use the program.

Explain all the fun idiosyncrasies of rebooting between Windows and *nix operating systems

provisioner:
  name: chef_zero
  max_retries: 3 # tweak in conjunction with below
  wait_for_retry: 90 # tweak based on machine shutdown speed
  retry_on_exit_code:
    - 35 # chef-client's reboot scheduled exit status
  client_rb:
    exit_status: :enabled # default in 13+
    client_fork: false # don't fork so we get true exit code

Wish I had time to add this myself today, but it might be useful to reference

http://www.hurryupandwait.io/blog/creating-windows-base-images-for-virtualbox-and-hyper-v-using-packer-boxstarter-and-vagrant

as well as available images in Atlas, e.g.

https://atlas.hashicorp.com/opentable/boxes/win-2012r2-standard-amd64-nocm

Shouldn't we recommend install Chef DK instead of the gem based solution?
https://downloads.getchef.com/chef-dk/

@calebhailey what is meant there?
https://github.com/test-kitchen/kitchen-docs/blame/master/source/docs/getting-started/running-verify.md#L49

The correct URL is https://docs.chef.io/berkshelf.html w/o trailing slash.

Cheers
Christopher

See test-kitchen/test-kitchen#1432

It's problematic and since it's meant to be a toy example let's pick something else.

Chef 14.3+ can silence deprecation warnings as per https://github.com/chef/chef/blob/master/RELEASE_NOTES.md#silencing-deprecation-warnings

provisioner:
  name: chef_solo
  solo_rb:
    treat_deprecation_warnings_as_errors: true
    silence_deprecation_warnings:
    - deploy_resource
    - chef-23
    - recipes/install.rb:22

Ran into a issue the the instructions following the creating-cookbook kitchen create where upon booting the VM the SSH key couldn't be created. Command just paused at :

==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key

Running on:

• Chef: 12.16.42
• Vagrant Version: 1.8.7
• VirtualBox: 5.0.30
• Mac OS X: 10.11.6

Fix was found here http://stackoverflow.com/a/40142286/7216518 and involved a edit the .kitchen.yaml to enabled cableconnected1: on

driver:
  name: vagrant
  customize:
    cableconnected1: 'on'

Also while not a issue with kitchen I will include here in case anyone finds it, as I needed to fix to get this far:

Curl broken in macOS vagrant 1.8.7 hashicorp/vagrant#7997
Workaround:

sudo rm -f /opt/vagrant/embedded/bin/curl

provisioner:
  name: chef_zero
  environments_path: test/environments
  client_rb:
    environment: kitchen

For posterity we should note solo_rb vs client_rb even though nobody should need it at this juncture. Also note files in environments_path must be JSON

As @cheeseplus suggested, I'm giving you an actionable request to improve the docs. Having the FAQ where it is made it invisible to me. We should be able to navigate to it from the Getting Started Guide as an item below Next Steps.

Document how to use these and what they are commonly used for

Moving test-kitchen/test-kitchen#1054 here.

transport:
  name: winrm
  elevated: true

...and redirect http://kitchen.ci/ to https://kitchen.ci/. Security, integrity and privacy first! 😃

running-test has the same contents as adding-platform, the content seems to belong to adding-platform

The links from "and the folks over at the #learnchef website have a handy Workstation Setup that we can follow to get us started" are broken.

I forked the docs and added some links to the individual sites (Chef, Vagrant, Git and VirtualBox) because I couldn't find a combined page anymore. I'm happy to create a pull-request, or add the file here, but I read I should discuss on IRC first. Can't find anyone over there to discuss with. Maybe I need to wait longer.

Let me know the best thing to do. Ta