min version for win32-process is 0.7.1

- win2k3r2 is broken in 0.7.0 see:

https://github.com/djberg96/win32-process/issues/8
Add scripts to run the specs on Jenkins.
remove Associated Press Breaking API gem dep

- my guess is awesome_print used to be called 'ap'?
[MIXLIB-7] remove awesome_print
Remove cruft
Update mock/stubs to avoid deprecations
Force subprocess to exit after timeout

Fixes MIXLIB-16.

This issue is particularly prominent when yum/rpm commands go off the
deep end repeatedly, but affects any case where a process takes longer
than the timeout to complete.
Cleanup control flow in main loop

removes some complexity that was introduced with the fix to kill
timed-out child processes
Add logging about timed-out cmd termination when possible

If a logger is configured, send `error` level messages about child
process termination for timeout violations.
Add termination info to error messages

If no logger is configured, we still want to inform the user that the
process was killed (and how).
Bump the version number for release.
Clean up `jenkins_run_tests.bat`

This change ensures the bat file is in sync with what we have in
opscode/chef.
Silence `:rubygems` Bundler deprecation notice.

Message from Bundler before this change:

  The source :rubygems is deprecated because HTTP requests are insecure.

  Please change your source to 'https://rubygems.org'; if possible, or
  'http://rubygems.org'; if not.
Remove -b from default rspec options

RSpec seems to be much better at filtering nowadays and the extra lines
are a PITA in development.
Run timeout tests without a subshell

/bin/sh on Ubuntu is dash, which does not support bash's behavior of
using exec to run a command (instead of fork) when possible. This means
that, when given a single string command, instead of an array of command
plus arguments, the process created by fork/exec is dash, and the ruby
program is a child process of dash. When shellout signals the child to
exit after a timeout, it will signal dash instead of the ruby program.

To avoid this issue, the command needs to be given as an Array to avoid
creating a subshell.
Run commands with unique pgid to improve timeout cleanup

To ensure that all child processes are properly signaled to exit before
forcibly killing them, use `setsid()` in the child process to give the
child (and any grandchildren it might create) a new and unique process
group. If the command times out, kill and reap the entire process group.
Always send KILL to process group

There is not a good way to reliably detect whether all grandchildren
have exited after sending a TERM to the process group; if the child has
correctly exited, grandchildren (which may be unresponsive) will have
been adopted by init (ppid == 1) so the parent cannot wait() on them. To
ensure no stuck grandchildren are left, send a KILL to the process group
after allowing the processes time to clean up.
Add travis yaml
Adds error? method to check whether the process exited successfully. This allows the user to use custom error-handling logic. error! now uses error? internally.