| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
I'm also adding these same examples to the docs.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
It helps to not pass a nil in
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Formatting fixes and updates to the text to make the generated text match what's currently on the site.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Update some of our build docs to reflect the current process. Nuke the old Travis config. We're Buildkite + appveyor only at this point.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
|
|
| |
Add examples in markdown to the resources. We'll be using this on the
docs site in the future and if we need to display it we can use
tty-markdown which does a really nice job of displaying markdown in the
terminal
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\
| |
| | |
More Chefstyle updates
|
| |
| |
| |
| |
| |
| | |
since we use double quotes, be consistent everywhere.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| |
| |
| | |
start enforcing using %i{} instead of arrays of symbols
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| |
| |
| |
| | |
i like this one, gives visual priority to returns or raises that are
buried in the middle of things.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| | |
Also prevent more extra spaces
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/
|
|
|
|
|
|
|
| |
1) Fix the indentation
2) Avoid extra new lines
3) Show example data if we have it
4) Chef Infra Client vs. the Chef Infra Client
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Help out anyone stumbling upon this to know the backstory
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
|
|
| |
This adds a new feature to chef-client where users must accept the
EULA before using the product. Users can accept the license by
passing '--chef-license accept', setting ENV[CHEF_LICENSE]=accept or by
running 'chef-client' and following the interactive prompt.
Signed-off-by: tyler-ball <tball@chef.io>
|
|
|
|
|
|
| |
This process is being replaced with our new owners process as outlined in https://github.com/chef/chef-oss-practices
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
We don't do pre-releases anymore so there's no point in doing this.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
| |
It's PowerShell not Powershell. Our docs site had already been updated.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
See also https://github.com/chef/chef-rfc/pull/322
Signed-off-by: Nathen Harvey <nharvey@chef.io>
|
|
|
|
|
|
|
|
| |
we're calling scripts to call rake tasks to call scripts to call rake
tasks to mostly execute shellcodes. this gets rid of at least 2 levels
of indirection.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
| |
mixlib-install has been out long enough at this point we don't need to
call it new or mention what version of DK originally shipped with it.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
This was in DK before, but it made no sense there. This might convince some folks to test things when we cut a pre-release.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
This cookbook is gone and this causes this job to fail
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
| |
absolutely hard requirement on the fixes that went into chef-config 2.2.11, so the
floor of that gem is bumped up.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
|
| |
We haven't used this framework for 2 major releases of Chef and as time goes on it's more and more likely we'll build something very different for testing.
We 100% do need acceptance testing, but between dokken testing in Travis and the potential for more complex integration testing with build-kite I think we should do the proper cleanup and remove this code now.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
goes red because we're really red here
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
This reverts commit 2865ca316e5b9512ffd8a7d784355e469a115717.
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
| |
We're probably going to see some more failures with this change, but that's a good thing. If we have a bad kitchen change or a bad cookbook change we'll know now earlier. Less impact == better.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Add the chef-config unit tests to the unit testing group
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Thom May <thom@may.lt>
|
|\
| |
| | |
Update Expeditor config to use new Merge and Artifact Actions
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Chef Expeditor now supports built in merge and artifact actions which
allow us to reduce the burden of duplicating common processes across
all our repositories. This change introduces several of these built_in
functions, replacing functionality that was previously kept in our
Rakefile.
Signed-off-by: Tom Duffield <tom@chef.io>
|
|/
|
|
|
|
|
|
|
|
| |
* Remove call to update_omnibus_overrides
The rake tasks `update_omnibus_overrides` was removed in dafd5139338aed684410e311b9be906b346db678.
* Update acceptance/Gemfile.lock to match Gemfile.lock for mixlib-shellout
This should fix acceptance where we're seeing both mixlib-shellout 2.3.1 and 2.3.2.
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Thom May <thom@chef.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
this is also necessary for bundler-1.14.x
i'm still not entirely clear why we ever needed all the fussy software gem
configs or what the build-chef / build-chef-gem infrastructure ever
did for us. it seems to have been mostly micro-optimization around
building the software gems before bundle installing the project in order
to take advantage of git caching. i aggressively don't care about that,
this is quite fast enough. we can install nokogiri and libgecode early
and that should take care of 98% of the build optimization issue.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
See the PR comments for more philosophical background.
This simplifies the external tests. The major feature here is that
halite, poise, chefspec, etc are removed from the Gemfile.lock and
the transitive Gemfile splicing is gone from the external tests.
We're back to simply tracking master on external projects and bundle
installing without locks and going red if the break. Those external
projects should all similarly track master of chef/chef to reduce
the possibility that they break us here.
This also bumps bundler to 1.14.x and unblocks us there.
It continues to simplify our use of bundler to be more mainstream and
less impenetrable.
There was some crazy shit that I found where I had to remove env vars
like BUNDLE_ENABLE_TRAMPOLINE and the BUNDLE_IGNORE_CONFIG and
BUNDLE_FROZEN env vars in appveyor along with the .bundle/config frozen
setting were necessary to unbreak appveyor. We seem to have gotten
very far afield of standard bundler usage and it was breaking in strange
to debug ways.
Oddly enough this exposed weird errors in the
chef-config/spec/units/fips_spec.rb tests where we need to require the
"win32/registry" file there now even though I can't figure out why that
broke or how it was working previously.
Also, adding x64-mingw32 to x86-mingw32 was necessary to test in
appveyor on 64-bit windows (I tried universal-mingw32 and that failed)
which seems obvious and is another case that I don't understand how it
was working in bundler 1.12.x
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
applies the same kinds of fixes that i applied to rake dependencies:*
and mostly reverts to mainline usage of bundler. abandons all the
trampolining, and uses the platforms that are already locked in
the Gemfile.lock and unwinds the multi-platform stuff that bundler
does natively now.
removes the BundleUtil module entirely since it is no longer used.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|