| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
There's no reason to keep executing our TK tests against ruby 2.4.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: dheerajd-msys <dheeraj.dubey@msystechnologies.com>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
| |
running rspec inside a test-kitchen provisioned centos-7 docker container
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Seth Thomas <sthomas@chef.io>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
We've deployed a new omnitruck release which should correct the version
identification bug we had before.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Stuart Preston <stuart@chef.io>
|
|
|
|
|
|
| |
It's our end-to-end test according to the readme. This just aligns the recipe/suite names with that so it's a bit more obvious what we're doing here. This also removes sudo installs since I moved that all to dokken-images now.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
|
| |
Awesome customers cookbook testing isn't even correct from learn chef anymore and it's not coming back in this form. There's no reason to keep carrying it around.
This change also deps on kitchen 1.21 and uses the new name for the configs. Much easier to find if you're browsing the source in Finder/Explorer.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\
| |
| | |
actually test against cheffs
|
| |
| |
| |
| |
| |
| | |
goes red because we're really red here
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|/
|
|
|
|
| |
it doesn't depend on chef/chef so this test seems quite pointless.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
| |
Disable this pending a Chef 14 compatible version of poise
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Not sure how this got in there, but we certainly don't need it.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|\
| |
| | |
Don't try to install old GCC packages on Amazon Linux 2
|
| |
| |
| |
| |
| |
| | |
It's enough different and we're starting to get a good number of users on the new version.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/
|
|
| |
Signed-off-by: Thom May <thom@chef.io>
|
|
|
|
|
|
| |
Copied as is with the new description fields added.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
We have a dokken image for 18.04 based off the beta and rebuilding on a schedule in Docker Cloud.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
| |
A spec here was accidentally dropping privs from root which was causing
subsequent chaos with file perms issues in later specs.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
| |
This seems to make unit tests on travis somewhat more stable
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
| |
Debian 7 goes EOL 31st May 2018
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Thom May <thom@chef.io>
|
|
|
|
| |
Signed-off-by: Thom May <thom@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
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: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
It should all pass now
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
This isn't coming back. We'll replace it with the learnchef stuff in another PR.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@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>
|