| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
when bumping version and updating dependencies
|
| |
|
| |
|
| |
|
|
|
|
| |
version is installed
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will ensure the path to the suites can be fully resolved, it
prevents errors like:
```
STDERR:
/home/jenkins/workspace/chefdk-test/architecture/x86_64/platform/acceptance/project/chefdk/role/tester/vendor/bundle/ruby/2.1.0/gems/mixlib-shellout-2.2.6/lib/mixlib/shellout/unix.rb:183:in
`chdir': No such file or directory @ dir_chdir -
/home/jenkins/workspace/chefdk-test/architecture/x86_64/platform/acceptance/project/chefdk/role/tester/opscode-ci/.acceptance/acceptance-cookbook
(Errno::ENOENT)
```
|
|
|
|
| |
This reverts commit aac62e28ae3112c586f223c48ef7fe360f98e56a.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
We output all data generated during a chef-acceptance run to the workspace
of the executing Jenkins job using chef-acceptance's `--data-path` option.
If the `chef-acceptance` commands are executed with elevated privileges
(using `sudo`) the generated files are owned by `root`:
https://gist.github.com/schisamo/7ce7262813f2bc81b7314d9eab53afa0
This is an issue as the generated data cannot be properly archived OR
cleaned up when the next job runs:
https://gist.github.com/schisamo/b7246987d49534b27b8a4ad72f9ad965
|
|
|
| |
See https://github.com/chef/chef/blob/master/acceptance/.shared/kitchen_acceptance/libraries/kitchen.rb#L19
|
|
|
|
|
|
|
|
| |
Previously data was being written to the Chef package install path of
`/opt/chef/*/acceptance/*` which is bad for numerous reasons. Now that
chef/chef-acceptance#39 has been merged we can take advantage of Chef
Acceptance's new `--data-path` option which allows us to relocate this
directory into the Jenkins job's workspace for easy archiving.
|
|
|
|
| |
These have not been needed since: chef/mixlib-install#90
|
| |
|
| |
|
|
|
|
| |
Chef tess
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Travis/Appveyor already run the unit tests at the appropriate gate
earlier in the build process. Running the tests on each platform we build
a package for should give the same result and really just serves to slow
the overall delivery process down.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
The if statement was always being evaluated to true.
|
|
|
|
|
|
|
|
|
|
|
| |
Some testers fail with
```
ci/verify-chef.sh: test: ] missing`
```
This regression was introduced by
https://github.com/chef/chef/commit/2bcb7d06dcb49c953b9e666b24c8bd3cb56da2c5
|
| |
|
| |
|
|
|
|
|
| |
Use bundle exec to run rspec.
Launch chef-client with ruby so that it launches correctly on windows.
|
|
|
|
|
| |
E.g., system ruby may be used instead of the intended ruby if there is a
ruby in /usr/local/bin
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
.gitattributes
chef-expander/Rakefile
chef-expander/lib/chef/expander/version.rb
chef-server-api/Rakefile
chef-server-api/chef-server-api.gemspec
chef-server-api/lib/chef-server-api/version.rb
chef-server-webui/Rakefile
chef-server-webui/chef-server-webui.gemspec
chef-server-webui/lib/chef-server-webui/version.rb
chef-server/Rakefile
chef-server/lib/chef-server/version.rb
chef-solr/lib/chef/solr/version.rb
chef.gemspec
chef/Rakefile
chef/spec/support/platform_helpers.rb
chef/spec/support/shared/functional/file_resource.rb
chef/spec/unit/api_client_spec.rb
chef/spec/unit/provider/directory_spec.rb
ci/jenkins_run_tests.bat
ci/jenkins_run_tests.sh
distro/common/html/chef-client.8.html
distro/common/html/chef-expander.8.html
distro/common/html/chef-expanderctl.8.html
distro/common/html/chef-server-webui.8.html
distro/common/html/chef-server.8.html
distro/common/html/chef-shell.1.html
distro/common/html/chef-solo.8.html
distro/common/html/chef-solr.8.html
distro/common/html/knife-bootstrap.1.html
distro/common/html/knife-client.1.html
distro/common/html/knife-configure.1.html
distro/common/html/knife-cookbook-site.1.html
distro/common/html/knife-cookbook.1.html
distro/common/html/knife-data-bag.1.html
distro/common/html/knife-environment.1.html
distro/common/html/knife-exec.1.html
distro/common/html/knife-index.1.html
distro/common/html/knife-node.1.html
distro/common/html/knife-role.1.html
distro/common/html/knife-search.1.html
distro/common/html/knife-ssh.1.html
distro/common/html/knife-status.1.html
distro/common/html/knife-tag.1.html
distro/common/html/knife.1.html
distro/common/man/man1/chef-shell.1
distro/common/man/man1/knife-bootstrap.1
distro/common/man/man1/knife-client.1
distro/common/man/man1/knife-configure.1
distro/common/man/man1/knife-cookbook-site.1
distro/common/man/man1/knife-cookbook.1
distro/common/man/man1/knife-data-bag.1
distro/common/man/man1/knife-environment.1
distro/common/man/man1/knife-exec.1
distro/common/man/man1/knife-index.1
distro/common/man/man1/knife-node.1
distro/common/man/man1/knife-role.1
distro/common/man/man1/knife-search.1
distro/common/man/man1/knife-ssh.1
distro/common/man/man1/knife-status.1
distro/common/man/man1/knife-tag.1
distro/common/man/man1/knife.1
distro/common/man/man8/chef-client.8
distro/common/man/man8/chef-expander.8
distro/common/man/man8/chef-expanderctl.8
distro/common/man/man8/chef-server-webui.8
distro/common/man/man8/chef-server.8
distro/common/man/man8/chef-solo.8
distro/common/man/man8/chef-solr.8
lib/chef/api_client.rb
lib/chef/rest.rb
lib/chef/version.rb
spec/functional/knife/ssh_spec.rb
spec/functional/resource/cookbook_file_spec.rb
spec/spec_helper.rb
spec/stress/win32/security_spec.rb
spec/support/shared/functional/securable_resource.rb
spec/unit/config_spec.rb
spec/unit/knife/ssh_spec.rb
|
| |
| |
| |
| | |
too much windows in that moment there; need to exit and not return
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
...should help avoid pollution of global state from unit tests
|
|
|
|
|
|
| |
Chef 10 and 11 differ in directory structure so lets add a script to ease that
This also exposes our testing a bit so other people know what we are doing
interally.
|
| |
|
|
|
|
| |
...should help avoid pollution of global state from unit tests
|