summaryrefslogtreecommitdiff
path: root/.travis.yml
Commit message (Collapse)AuthorAgeFilesLines
* Disable sudo on unit testslcg/travis-tetingLamont Granquist2018-02-201-6/+6
| | | | | | This seems to make unit tests on travis somewhat more stable Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Remove testing of Debian 7bye_debian_7Tim Smith2018-02-041-17/+0
| | | | | | Debian 7 goes EOL 31st May 2018 Signed-off-by: Tim Smith <tsmith@chef.io>
* [ci skip] add comment about why we do what we do hereLamont Granquist2018-01-251-0/+3
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* allow uninstall of bundler to faillcg/uninstall-bundler-failsLamont Granquist2018-01-251-2/+2
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* see what up with the proxy teststm/proxy_testsThom May2018-01-231-0/+1
| | | | Signed-off-by: Thom May <thom@chef.io>
* start branch for 14Thom May2018-01-191-35/+13
| | | | Signed-off-by: Thom May <thom@chef.io>
* Add Ruby 2.5 testing to TravisTim Smith2018-01-181-0/+20
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Update to Ruby 2.4.3ruby243Tim Smith2018-01-051-27/+27
| | | | | | | | | This resolves this CVE https://www.ruby-lang.org/en/news/2017/12/14/net-ftp-command-injection-cve-2017-17405/ It also backports a few bugfixes from 2.5.0: https://github.com/ruby/ruby/compare/v2_4_2...v2_4_3 Signed-off-by: Tim Smith <tsmith@chef.io>
* Don't run sudo on every travis jobtravis_speedupTim Smith2018-01-041-1/+0
| | | | | | | We already specify sudo where we need it. Enabling it everywhere just means we have to run full boxes that take longer to spin up. Signed-off-by: Tim Smith <tsmith@chef.io>
* Remove the Gemfile.lock and Berksfile.lock for kitchen testsintegration_docsTim Smith2017-12-221-13/+0
| | | | | | 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>
* Break out unit/integration/functional tests in travis and test chef-configTim Smith2017-12-201-6/+36
| | | | | | Add the chef-config unit tests to the unit testing group Signed-off-by: Tim Smith <tsmith@chef.io>
* Fail if we can't modify the sudoers fileTim Smith2017-12-201-1/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Remove duplicate amazon linux test in the travis configTim Smith2017-12-071-25/+4
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Remove the allowed_failures in TravisTim Smith2017-12-071-1/+0
| | | | | | It should all pass now Signed-off-by: Tim Smith <tsmith@chef.io>
* Fix the name of the opensuse kitchen boxTim Smith2017-12-041-1/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Add opensuse testing to TravisTim Smith2017-12-011-0/+18
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Remove the old amazon travis defamazon_testingTim Smith2017-12-011-18/+0
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Add Amazon Linux kitchen run to TravisTim Smith2017-11-301-0/+18
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Turn back on Fedora testing in TravisTim Smith2017-11-281-18/+18
| | | | | | | Use the new openssh cookbook which has a Fedora fix Turn off use_privilege_separation which doesn't work on Fedora Signed-off-by: Tim Smith <tsmith@chef.io>
* Switch from the Travis container to the VMbtm/travisBryan McLellan2017-11-221-1/+1
| | | | | | | | | | | | | If `sudo` is `false`, then Travis CI will use a container for testing. If `sudo` is `required, then it will use a GCE VM. We've recently been seeing permission errors that appeared related to the Travis CI infrastructure. Switching to the VM resolves those errors. The downside is that it takes 50s instead of 5s to start up the tester, but given that our tests take 18 minutes that is okay. https://docs.travis-ci.com/user/reference/trusty/ Signed-off-by: Bryan McLellan <btm@loftninjas.org>
* Remove the webapp cookbook from integration testsTim Smith2017-09-181-10/+10
| | | | | | This isn't coming back. We'll replace it with the learnchef stuff in another PR. Signed-off-by: Tim Smith <tsmith@chef.io>
* Test on the latest Ruby and disable Amazon Linux testingTim Smith2017-09-181-43/+43
| | | | | | It's been failing for a LONG time. We need to fix it, but lets not waste cycles for now Signed-off-by: Tim Smith <tsmith@chef.io>
* Add Debian 9 testingTim Smith2017-09-181-0/+18
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Update the chefspec URL for TravisTim Smith2017-06-081-1/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* simplify omnibus config and greenify builds againLamont Granquist2017-05-091-16/+16
| | | | | | | | | | | | | | 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>
* switch to using trusty on travisLamont Granquist2017-05-021-2/+1
| | | | | | | the travis precise openssl libs appears to hate rubygems and we should do this anyway. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* bonus fix for failing chef-zero teststm/litaThom May2017-04-281-0/+1
| | | | Signed-off-by: Thom May <thom@chef.io>
* major testing overhaullcg/simplify-external-testsLamont Granquist2017-04-251-49/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* Enable travis testing for chef-12 branchtm/en_travisifyThom May2017-04-101-1/+1
| | | | Signed-off-by: Thom May <thom@chef.io>
* Remove 12.04 testing in Travisintegration_test_tweaksTim Smith2017-04-051-18/+0
| | | | | | 12.04 is goes EOL on 4/28. http://fridge.ubuntu.com/2017/03/15/ubuntu-12-04-precise-pangolin-reaches-end-of-life-on-april-28-2017/ Signed-off-by: Tim Smith <tsmith@chef.io>
* Remove duplicate bundler_args from TravisTim Smith2017-04-051-1/+0
| | | | | | This is in here twice and the YAML is invalid. They’re duplicate Signed-off-by: Tim Smith <tsmith@chef.io>
* add back amazon and allow failuresLamont Granquist2017-04-031-18/+37
| | | | | | this will probably help with debugging it seems like a bit of a mess Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* openssh cookbook is busted with amazonlinuxLamont Granquist2017-04-031-18/+18
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* drop 2.2 support + testing / bump tests to 2.4.1Lamont Granquist2017-03-281-27/+22
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* bump ruby to 2.4.1Lamont Granquist2017-03-281-1/+1
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* re-enable amazon linux tests we had to disableLamont Granquist2017-03-201-19/+18
| | | | | | these work now. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Chef-13: remove Chef::Platform.set and related methodsLamont Granquist2017-03-171-37/+37
| | | | | | Switch over the Chef-12.0 ProviderResolver is now completed. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Merge pull request #5869 from chef/tm/no_provisioning_testsThom May2017-03-081-4/+0
|\ | | | | Remove provisioning from the downstream tests
| * Remove provisioning from the downstream teststm/no_provisioning_testsThom May2017-03-071-4/+0
| | | | | | | | Signed-off-by: Thom May <thom@chef.io>
* | Replace changelog group with ci groupTom Duffield2017-03-071-19/+19
|/ | | | Signed-off-by: Tom Duffield <tom@chef.io>
* add a comment on knife-windows test disablingLamont Granquist2017-02-281-0/+3
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Bump chef version to 13.0.0Lamont Granquist2017-02-281-4/+4
| | | | | | | | | | | 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>
* disable chefspec testingLamont Granquist2017-02-261-11/+11
| | | | | | | | it needs fixing for chef-13 backcompat breaks (all those deprecation warnings in its logs turn out to be bad) Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* fix the bundler pinningLamont Granquist2017-01-231-0/+6
| | | | | | | | - remove all versions of the gem before installing the one we want - ensure that if the travis version is more recent that we don't pick it up - also add some debugging output of the versions afterwards Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* comment out amazonlinux for nowLamont Granquist2017-01-131-18/+19
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* be more patient with amazonlinuxLamont Granquist2017-01-121-1/+1
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* enforce 2.4.0 failuresLamont Granquist2017-01-111-3/+0
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* just comment out fedora-latestLamont Granquist2017-01-111-23/+18
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* ignore fedora-latestLamont Granquist2017-01-111-0/+5
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* ruby-2.4 got releasedlcg/ruby-2.4Lamont Granquist2017-01-111-2/+2
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
View Lorry Controller Status