summaryrefslogtreecommitdiff
path: root/Gemfile
Commit message (Collapse)AuthorAgeFilesLines
* fix retries on JSON POST requests when negotiating protocol versionLamont Granquist2017-07-201-0/+1
| | | | | | | | | | | | | | | | | | | | | | on the first pass through the JSON middleware it encodes the body. if there's a retry, it re-encodes the body as a string with all its metacharacters escaped. this is a particular issue when doing a first request that is a POST that requires negotiating the API version. when doing a GET it isn't a problem because there's no body payload -- but a POST or a PUT which requires a retry will get garbled and will cause a 500. this happens on hosted right now if trying to POST with a v2 API since hosted is only v1, so there's a retry to downgrade. i also made the same kind of changes to the streaming download requests, but since they're GETs its unclear to me if there was any impact there -- but middleware could have been double-mangling headers on a retry. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* move nokogiri config to omnibusLamont Granquist2017-07-101-1/+0
| | | | | | | | | this hand-builds it with the software dep, and its not a direct dep of chef itself and shouldn't be in the Gemfile.lock anyway, plus we need to pin via omnibus_overrides.rb and double-pinning in the Gemfile.lock is just added fussiness Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Should be happier now.Noah Kantrowitz2017-07-051-2/+1
| | | | Signed-off-by: Noah Kantrowitz <noah@coderanger.net>
* update commentLamont Granquist2017-05-241-1/+1
|
* use eval_gemfileLamont Granquist2017-05-241-1/+1
|
* simplify omnibus config and greenify builds againLamont Granquist2017-05-091-3/+2
| | | | | | | | | | | | | | 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>
* actually i don't think appveyor needs thislcg/remove-bundler-againLamont Granquist2017-04-271-3/+0
| | | | | | | pretty sure i solved this some other way and this was debugging i forgot to remove... Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* major testing overhaullcg/simplify-external-testsLamont Granquist2017-04-251-22/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* Use Ohai 13.0.0 releasetm/release_notesThom May2017-04-061-2/+1
| | | | Signed-off-by: Thom May <thom@chef.io>
* Add InSpec to chef omnibus buildsadamleff/add-inspecAdam Leff2017-04-051-0/+1
| | | | | | | | | | | | | This change adds InSpec to the Chef Gemfile, making it easier for our community to use InSpec for testing without requiring them to `chef_gem` install it prior to use. This also helps our users who wish to use InSpec but are in an air-gapped environment. Including our preferred testing library in our Omnibus builds will make it much easier for those users to use InSpec. Signed-off-by: Adam Leff <adam@leff.co>
* RFC 67: Remove cookbook segmentsThom May2017-04-041-1/+1
| | | | | | | | | This implements RFC 67, which removes cookbook segments, and moves to a single list of all the files contained in a cookbook. This allows us to move forward with better audit modes and also proper shipping of ohai plugins. Signed-off-by: Thom May <thom@chef.io>
* disable shipping nokogiri on windows for nowLamont Granquist2017-03-291-2/+2
| | | | | | | | | | | | nokogiri does not have a ruby-2.4 release for windows this is slightly complicated because we still need nokogiri in the Gemfile.lock for travis. i'm starting to think we should have a Gemfile.travis and Gemfile.travis.lock or something and stop using groups for that. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Bump nokogiri for CVE-2016-4658Maxime Brugidou2017-03-241-1/+2
| | | | | | | | | https://github.com/sparklemotion/nokogiri/issues/1615 This is required to pass the bundle-audit check in Travis CI Change-Id: Ia34db5b0595b88560fdff36a451df7567907e727 Signed-off-by: Maxime Brugidou <m.brugidou@criteo.com>
* Remove provisioning from the downstream teststm/no_provisioning_testsThom May2017-03-071-1/+0
| | | | Signed-off-by: Thom May <thom@chef.io>
* Merge pull request #5834 from chef/tduffield/update-version-bumpingTom Duffield2017-03-071-2/+2
|\ | | | | Improve version bumping
| * Better handle version bumpingtduffield/update-version-bumpingTom Duffield2017-02-221-2/+2
| | | | | | | | Signed-off-by: Tom Duffield <tom@chef.io>
* | Bump chef version to 13.0.0Lamont Granquist2017-02-281-3/+6
|/ | | | | | | | | | | This requires pulling in master of several gems, bumps all the other gems, plus pulls in new kitchen-appbundle-updater which supports pulling master of ohai. Note that kitchen-windows is disabled because it turns out it was broken and red on 12.19 all along. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Add back a few gems that are required (and document why)Tom Duffield2017-02-091-1/+1
| | | | Signed-off-by: Tom Duffield <tom@chef.io>
* Cleanup Gemfiles, Berksfiles, and update Gemfile groupsTom Duffield2017-02-091-2/+3
| | | | Signed-off-by: Tom Duffield <tom@chef.io>
* Remove a lot of old restraintsTom Duffield2017-02-091-1/+1
| | | | Signed-off-by: Tom Duffield <tom@chef.io>
* remove chef-provisioning-awslcg/remove-chef-provisioningLamont Granquist2016-12-201-1/+0
| | | | | | blocks testing on ruby 2.4 Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Use tduffield branch of github-changelog-generatorTom Duffield2016-12-021-1/+2
| | | | | | | | | | | | This branch fixes a number of bugs in the changelog generator, and supports the type of behavior that we want when generating our changelog. There is a PR open against upstream (skywinder/github-changelog-generator#453) to merge this upstream. As part of this, we can now generate the changelog on every commit. Signed-off-by: Tom Duffield <tom@chef.io>
* we haven't even been testing against chef-rewind for some timeLamont Granquist2016-10-071-1/+0
| | | | | | | | and its now officially deprecated in its README: https://github.com/thommay/chef-rewind Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* update dependencies (#5384)Matt Wrock2016-09-261-1/+1
|
* Bring in cucumber to prevent cucumber-core from being wrongly loadedJohn Keiser2016-09-081-1/+2
|
* Pin oc-chef-pedant to prevent unintended test slippageJohn Keiser2016-09-081-0/+3
|
* yet another dependency update PRupdate-depsMatt Wrock2016-09-071-0/+2
|
* Chefspec 5.0 is out. Remove fetching from git masterTim Smith2016-08-251-1/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* remove ruby 2.1 supportLamont Granquist2016-08-221-1/+0
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* switch to https urlLamont Granquist2016-08-191-1/+1
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* track master of chefspec for fixesLamont Granquist2016-08-191-1/+1
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Put travis and github gems back on released versionsjk/update-github-apiJohn Keiser2016-08-101-4/+1
|
* Update all dependenciesJohn Keiser2016-08-031-0/+4
|
* Install nokogiri and pin mixlib-cliksubrama/nokogiriKartik Null Cating-Subramanian2016-07-151-0/+1
| | | | | See https://github.com/chef/chef-dk/pull/937 and https://github.com/chef/chef/issues/5116
* Comment why we're pinning rackTim Smith2016-06-301-1/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Depend on rack < 2Tim Smith2016-06-301-1/+1
| | | | | | | | Rack 2.0 was released today and it requires Ruby 2.2+ now, which is breaking Travis runs on anything that depends on Chef. This should get our builds running again. Signed-off-by: Tim Smith <tsmith@chef.io>
* update nokogiri and dependenciesMatt Wrock2016-06-211-1/+0
|
* Ignoring the nokogiri CVE until we update to 1.6.8tyler-ball2016-06-161-1/+1
|
* Updating omnibus dependencies to take advantage of new msys2 toolchaintyler-ball2016-06-141-1/+2
|
* Ensure we install rake in CI (version bump)jk/install-rakeJohn Keiser2016-06-061-1/+1
|
* fix bundle locking on bundler 1.12 and enforce version we wantbun_1_11Matt Wrock2016-05-251-11/+6
|
* SERIOUSLY don't install ruby-shadow on windows.jk/ruby-shadow-windowsJohn Keiser2016-04-201-1/+1
|
* Re-add activesupport testsjk/activesupport-testsJohn Keiser2016-04-191-1/+0
|
* Update changelog generator to latestjk/update-changelogJohn Keiser2016-04-191-1/+1
| | | | (we have a lockfile now, so we are protected against inadvertent updates)
* Don't update fips serverspec Gemfile.lockJohn Keiser2016-04-181-5/+3
|
* Don't bundle install on testsJohn Keiser2016-04-181-1/+1
|
* Remove Gemfile.windows and put both platforms in Gemfile.lockJohn Keiser2016-04-181-1/+12
|
* Make gemfile_util capable of copying groups overJohn Keiser2016-04-181-5/+7
|
* Simplify external tests and make them work with Gemfile.lockJohn Keiser2016-04-181-7/+19
|
* Use locked dependencies to build chefJohn Keiser2016-04-181-1/+4
|
View Lorry Controller Status