Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
branch: master
Commits on Feb 25, 2013
  1. Fix chef-client install to conform to rubygems 2.0

    tipt0e authored
    In rubygems 2.0 rubygems::format has changed to rubygem::package as per http://blog.rubygems.org/2012/12/03/2.0.0-preview2.html. Using knife::bootstrap in a knife plugin will fail on starting chef-client because of this discrepancy.
Commits on Feb 21, 2013
  1. @sersut

    Merge pull request #642 from opscode/chef_windows_service

    sersut authored
    Chef-Client as Windows Service
  2. @sersut

    Enable chef-client windows_service to stop in a timely manner when sp…

    sersut authored
    …lay is configured with a high number.
Commits on Feb 20, 2013
  1. @sersut
  2. @adamedx

    Merge pull request #646 from opscode/chef-oc-4739-rebase

    adamedx authored
    Addition of Batch and Powershell resources for Windows
Commits on Feb 19, 2013
  1. @adamedx
  2. @adamedx
  3. @adamedx
  4. @adamedx

    Adding missing shared examples for execute, script, and windows scripts

    adamedx authored adamedx committed
  5. @adamedx

    OC-4739: OC-4748: Refactor tests to share examples across batch and p…

    adamedx authored adamedx committed
    …owershell resource specs
  6. @adamedx

    OC-4739: OC-4748: Create powershell and batch providers in core Chef

    adamedx authored adamedx committed
Commits on Feb 16, 2013
  1. @sersut

    Add a log message to differentiate chef-client runs initiated by the …

    sersut authored
    …service from the manual runs.
  2. @sersut
  3. @sersut
  4. @sersut
  5. @sersut

    Create chef-service-manager using distro/service_manager.rb to contro…

    sersut authored
    …l chef-service on windows platforms.
Commits on Feb 12, 2013
  1. @btm

    Release 11.4.0

    btm authored
  2. @btm

    CHEF-1292 Lower json stack depth tests to 301

    btm authored
    1001 was causing stack level too deep errors on 1.8.7. This is
    still a huge stack depth and 1001 was arbitrary.
  3. @btm
  4. @danielsdeleo @btm

    remove setup message, it's a race either way

    danielsdeleo authored btm committed
  5. @danielsdeleo @btm

    fix race in test setup

    danielsdeleo authored btm committed
    the heart of the test is confirming that the last 2 messages are p1
    releasing lock and then p2 acquiring it. The two messages confirm that
    the test case is set up correctly.
  6. @danielsdeleo @btm

    set sync=true on IPC in run lock tests

    danielsdeleo authored btm committed
  7. @danielsdeleo @btm

    ensure writes are flushed in run lock IPC

    danielsdeleo authored btm committed
  8. @btm

    11.4.0.rc.0

    btm authored
  9. @btm

    CHEF-3863: Return to not trusting the JSON gem at all

    btm authored
    Within days of relaxing to a pessmistic constraint on patch release there was
    a patch release with breaking changes. We'll have to go back to testing the
    latest version by hand again.
  10. @danielsdeleo
Commits on Feb 11, 2013
  1. @danielsdeleo

    rdoc json compat methods

    danielsdeleo authored
  2. @danielsdeleo
  3. @danielsdeleo
  4. @danielsdeleo
  5. @danielsdeleo

    mutate the incoming hash

    danielsdeleo authored
    I'd rather not, but this object should be local to the caller at this
    point so it seems less bad than creating a bunch more objects
  6. @danielsdeleo
  7. @danielsdeleo
Commits on Feb 7, 2013
  1. @btm
  2. @danielsdeleo @btm

    add additional synchronization to run lock spec

    danielsdeleo authored btm committed
Something went wrong with that request. Please try again.