| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
This makes sure we don't fail on the very slim chance that an OS generated file (lookin' at you, AIX) ends up in this directory and blocks deletion.
Signed-off-by: Scott Hain <shain@chef.io>
|
|
|
|
|
|
|
| |
doesn't matter, and if it did we should use the actual bundler
trampolining.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Thom May <thom@chef.io>
|
|
|
|
| |
Signed-off-by: Tom Duffield <tom@chef.io>
|
|
|
|
| |
Signed-off-by: Tom Duffield <tom@chef.io>
|
|
|
|
| |
Signed-off-by: Tom Duffield <tom@chef.io>
|
|
|
|
| |
Signed-off-by: Tom Duffield <tom@chef.io>
|
|
|
|
| |
Signed-off-by: Tom Duffield <tom@chef.io>
|
|
|
|
| |
Signed-off-by: Salim Afiune <afiune@chef.io>
|
|
|
|
|
|
|
|
| |
The build system passes in the necessary build arguments, buts its
beneficial to have the Dockerfile keep up to date with what the latest
stable version is in case people want to build their own.
Signed-off-by: Tom Duffield <tom@chef.io>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
The feature that we thought existed in the changelog generator doesn't
work exactly as expected. Until that functionality can be added, we're
disabling the automatic changelog generation.
Signed-off-by: Tom Duffield <tom@chef.io>
|
|
|
|
|
|
|
|
| |
The Github Changelog Generator threw an error about invalid
encoding. This never happened locally, and indications are that its
because of this environment variable.
Signed-off-by: Tom Duffield <tom@chef.io>
|
|
|
|
| |
Signed-off-by: Tom Duffield <tom@chef.io>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
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.
|