mirror of
https://github.com/inspec/inspec
synced 2024-11-10 07:04:15 +00:00
559d6d3178
* Modernize the kitchen config This is basically the same one we use in chef/chef * Modernize the omnibus deps * Remove cookbook constraints * Avoid security warnings when bundle installing * Use the ruby-cleanup project to slim the omnibus package We're using this in chef and DK to greatly reduce our artifact size. It's just a set of cleanup steps that are the same for all ruby omnibus projects. Signed-off-by: Tim Smith <tsmith@chef.io>
29 lines
1.2 KiB
Ruby
29 lines
1.2 KiB
Ruby
# encoding: utf-8
|
|
source 'https://rubygems.org'
|
|
|
|
# Install omnibus
|
|
# Sadly due to an ongoing msys2 issue, producing windows builds requires
|
|
# the two branches below.
|
|
# gem 'omnibus', github: 'chef/omnibus', branch: 'ksubrama/gcc_investigate'
|
|
|
|
# Use Chef's software definitions. It is recommended that you write your own
|
|
# software definitions, but you can clone/fork Chef's to get you started.
|
|
# gem 'omnibus-software', github: 'chef/omnibus-software', branch: 'ksubrama/ruby23'
|
|
|
|
# Use entries from chef's Gemfile
|
|
gem 'omnibus', git: 'https://github.com/chef/omnibus', branch: 'master'
|
|
gem 'omnibus-software', git: 'https://github.com/chef/omnibus-software', branch: 'master'
|
|
|
|
# This development group is installed by default when you run `bundle install`,
|
|
# but if you are using Omnibus in a CI-based infrastructure, you do not need
|
|
# the Test Kitchen-based build lab. You can skip these unnecessary dependencies
|
|
# by running `bundle install --without development` to speed up build times.
|
|
group :development do
|
|
# Use Berkshelf for resolving cookbook dependencies
|
|
gem 'berkshelf', '>= 7.0'
|
|
|
|
# Use Test Kitchen with Vagrant for converging the build environment
|
|
gem 'kitchen-vagrant', '~> 1.3.1'
|
|
gem 'test-kitchen', '~> 1.21'
|
|
gem 'winrm-fs', '~> 1.0'
|
|
end
|