| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
They have a ruby26 environment now. We should test with it.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
| |
This is no longer a supported release and we won't be building or
testing it at this point.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Chef repo has Expeditor subscriptions to other repos which
automatically create a PR to bump versions of those dependencies in Chef
when they're released. We were skipping all commits in Appveyor by 'Chef
Expeditor' to avoid testing the automatic version bump commits that
happen on every merge to master.
This change will only skip the version bumps.
Signed-off-by: Bryan McLellan <btm@loftninjas.org>
|
|
|
|
|
|
|
| |
- Avoid running on Expeditor changes
- Avoid running on CHANGELOG/RELEASE_NOTES changes
Signed-off-by: Bryan McLellan <btm@loftninjas.org>
|
|
|
|
|
|
|
| |
chef-14 branch doesn't exist yet, but this way we won't have to update
things when we fork
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Stuart Preston <stuart@chef.io>
|
|
|
|
| |
Signed-off-by: Stuart Preston <stuart@chef.io>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Stuart Preston <stuart@chef.io>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
| |
but ignore uninstall failures and use --force
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Stuart Preston <stuart@chef.io>
|
|
|
|
| |
Signed-off-by: Stuart Preston <stuart@chef.io>
|
|
|
|
| |
Signed-off-by: Thom May <thom@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
This makes it easier to follow and matches their Ruby guide
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
|
|
|
| |
As of Rubygems 2.7 bundler is a default gem and cannot be uninstalled.
Appveyor recently (11/19) changed and now has bundler as a default gem.
We'll stop stop trying to force a bundler version and track what Ruby gives us.
Signed-off-by: Bryan McLellan <btm@loftninjas.org>
|
|
|
|
| |
Signed-off-by: Thom May <thom@chef.io>
|
|
|
|
|
|
|
| |
@FeodorFitsner reports that https://github.com/appveyor/ci/issues/1657 has
been fixed for the VS 2015 images.
Signed-off-by: Bryan McLellan <btm@loftninjas.org>
|
|
|
|
| |
Signed-off-by: Bryan McLellan <btm@loftninjas.org>
|
|
|
|
| |
Signed-off-by: MSys <harikesh.kolekar@msystechnologies.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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: Thom May <thom@chef.io>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Tom Duffield <tom@chef.io>
|
|
|
|
|
|
|
|
| |
so we can roll back when we need to
looks like we need to
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Tom Duffield <tom@chef.io>
|
|
|
|
|
|
| |
Signed-off-by: NimishaS <nimisha.sharad@msystechnologies.com>
Signed-off-by: NimishaS <nimisha.sharad@msystechnologies.com>
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This reverts commit 3cb10016d142c45d5b2409ecb337b1b7bc295046.
|
|
|
|
| |
the ffi branch is necessary for AIX until that patch is merged.
|
|
|
|
| |
appveyor
|
| |
|
|
|
|
|
| |
Something is causing the 64bit tests to fail,
this should help narrow it down
|
|
|
|
|
| |
Our tests are getting backed up. 2 hours is unreasonable.
Removing ruby 2.0 32 bit from the matrix
|
| |
|
| |
|
|\
| |
| |
| | |
Update appveyor.yml to correct OS version
|
| |
| |
| |
| | |
Also rename os to Windows 2012 R2 to avoid confusion.
|
|/ |
|