inspec/omnibus/kitchen.yml

driver:
  name: vagrant
  forward_agent: yes
  customize:
    cpus: 4
    memory: 4096
  synced_folders:
    - ['..', '/home/vagrant/inspec']
    - ['../../omnibus', '/home/vagrant/omnibus']
    - ['../../omnibus-software', '/home/vagrant/omnibus-software']

provisioner:
  name: chef_zero
  attributes:
    vagrant:
      this_key_exists_so_we_have_a_vagrant_key: true
    omnibus:
      build_user:          vagrant
      build_user_group:    vagrant
      build_user_password: vagrant
      install_dir:         /opt/inspec

platforms:
  - name: centos-6
    run_list: yum-epel::default
  - name: centos-7
    run_list: yum-epel::default
  - name: debian-9
    run_list: apt::default
  - name: ubuntu-16.04
    run_list: apt::default
  - name: macos-11.15
    driver:
      box: tas50/macos_10.15
      synced_folders:
      - ['..', '/Users/vagrant/chef']
      - ['../../omnibus', '/Users/vagrant/omnibus']
      - ['../../omnibus-software', '/Users/vagrant/omnibus-software']

  # The following (private) boxes are shared via Vagrant Cloud and are only
  # available to users working for Chef. Sorry, it's about software licensing.
  #
  # Chef-internal users, you will need to:
  # 1.  Create an Vagrant Cloud account:  http://vagrantcloud.com/
  # 2.  Ping #releng-support with your account name to be added to the relevant team.
  # 3.  Do `vagrant login` with your creds so that you can download the private boxes.
  #
  # The macOS boxes are VMware only also. You can enable VMware Fusion
  # by activating the `kitchen.vmware.yml` file with the `KITCHEN_LOCAL_YAML`
  # environment variable:
  #
  #   KITCHEN_LOCAL_YAML=kitchen.vmware.yml kitchen converge chef-macosx-1011
  #

  # By adding an `i386` to the name the Omnibus cookbook's `load-omnibus-toolchain.bat`
  # will load the 32-bit version of the MinGW toolchain.
  <% [ '', '-i386' ].each do |win_suffix| %>
  - name: windows-2012r2-standard<%= win_suffix %>
    driver:
      box: chef/windows-server-2012r2-standard # private
      synced_folders:
      # We have to mount this repos enclosing folder as the Omnibus build
      # gets cranky if the mounted source folder is a symlink. This
      # mounts at `C:\vagrant\code` and the inspec source folder is available
      # at `C:\vagrant\code\inspec`
      - ['../..', '/vagrant/code']
    provisioner:
      attributes:
        omnibus:
          build_user:          vagrant
          build_user_group:    Administrators
          build_user_password: vagrant
          install_dir:         /opscode/inspec
  <% end %>

suites:
  - name: inspec
    run_list: omnibus::default
add omnibus for inspec 2016-04-18 03:30:50 +00:00			`driver:`
			`name: vagrant`
			`forward_agent: yes`
			`customize:`
Improve windows support of omnibus installer - fix #889 2016-08-08 17:41:02 +00:00			`cpus: 4`
			`memory: 4096`
add omnibus for inspec 2016-04-18 03:30:50 +00:00			`synced_folders:`
[omnibus] Appbundle inspec and cleanup style issues - Removes resource files which matched the default implementations contained in omnibus. - Removes software definition for train which will be installed via the gem dependecies in the inspec defintion. - Appbundle inspec to match our other ruby-based projects - Update rubocop style violations - Update copyright notices Signed-off-by: Steven Danna <steve@chef.io> 2016-08-08 09:23:12 +00:00			`- ['..', '/home/vagrant/inspec']`
Improve windows support of omnibus installer - fix #889 2016-08-08 17:41:02 +00:00			`- ['../../omnibus', '/home/vagrant/omnibus']`
			`- ['../../omnibus-software', '/home/vagrant/omnibus-software']`
add omnibus for inspec 2016-04-18 03:30:50 +00:00
			`provisioner:`
			`name: chef_zero`
Improve windows support of omnibus installer - fix #889 2016-08-08 17:41:02 +00:00			`attributes:`
			`vagrant:`
			`this_key_exists_so_we_have_a_vagrant_key: true`
			`omnibus:`
			`build_user: vagrant`
			`build_user_group: vagrant`
			`build_user_password: vagrant`
			`install_dir: /opt/inspec`
add omnibus for inspec 2016-04-18 03:30:50 +00:00
			`platforms:`
Modernize omnibus config and reduce omnibus package size (#3543) * 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> 2018-10-29 20:01:45 +00:00			`- name: centos-6`
add omnibus for inspec 2016-04-18 03:30:50 +00:00			`run_list: yum-epel::default`
Modernize omnibus config and reduce omnibus package size (#3543) * 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> 2018-10-29 20:01:45 +00:00			`- name: centos-7`
add omnibus for inspec 2016-04-18 03:30:50 +00:00			`run_list: yum-epel::default`
Modernize omnibus config and reduce omnibus package size (#3543) * 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> 2018-10-29 20:01:45 +00:00			`- name: debian-9`
add omnibus for inspec 2016-04-18 03:30:50 +00:00			`run_list: apt::default`
Modernize omnibus config and reduce omnibus package size (#3543) * 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> 2018-10-29 20:01:45 +00:00			`- name: ubuntu-16.04`
add omnibus for inspec 2016-04-18 03:30:50 +00:00			`run_list: apt::default`
Enable repeatable builds by bundling Gemfile.lock This way changes to omnibus-software or omnibus don't change the builds. This is important for us, but also for cinc. It also makes sure that we're tracking bumps to the omnibus-software in the InSpec changelog so we can build release notes that reflect key dep changes like openssl. We recently added the same thing to Infra Server to better track deps there and we've done this in infra client for many years. Signed-off-by: Tim Smith <tsmith@chef.io> 2021-10-02 23:39:55 +00:00			`- name: macos-11.15`
			`driver:`
			`box: tas50/macos_10.15`
			`synced_folders:`
			`- ['..', '/Users/vagrant/chef']`
			`- ['../../omnibus', '/Users/vagrant/omnibus']`
			`- ['../../omnibus-software', '/Users/vagrant/omnibus-software']`

Modernize omnibus config and reduce omnibus package size (#3543) * 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> 2018-10-29 20:01:45 +00:00			`# The following (private) boxes are shared via Vagrant Cloud and are only`
Improve windows support of omnibus installer - fix #889 2016-08-08 17:41:02 +00:00			`# available to users working for Chef. Sorry, it's about software licensing.`
			`#`
			`# Chef-internal users, you will need to:`
Modernize omnibus config and reduce omnibus package size (#3543) * 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> 2018-10-29 20:01:45 +00:00			`# 1. Create an Vagrant Cloud account: http://vagrantcloud.com/`
			`# 2. Ping #releng-support with your account name to be added to the relevant team.`
			# 3. Do `vagrant login` with your creds so that you can download the private boxes.
Improve windows support of omnibus installer - fix #889 2016-08-08 17:41:02 +00:00			`#`
Modernize omnibus config and reduce omnibus package size (#3543) * 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> 2018-10-29 20:01:45 +00:00			`# The macOS boxes are VMware only also. You can enable VMware Fusion`
			# by activating the `kitchen.vmware.yml` file with the `KITCHEN_LOCAL_YAML`
Improve windows support of omnibus installer - fix #889 2016-08-08 17:41:02 +00:00			`# environment variable:`
			`#`
Modernize omnibus config and reduce omnibus package size (#3543) * 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> 2018-10-29 20:01:45 +00:00			`# KITCHEN_LOCAL_YAML=kitchen.vmware.yml kitchen converge chef-macosx-1011`
Improve windows support of omnibus installer - fix #889 2016-08-08 17:41:02 +00:00			`#`
Modernize omnibus config and reduce omnibus package size (#3543) * 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> 2018-10-29 20:01:45 +00:00
Improve windows support of omnibus installer - fix #889 2016-08-08 17:41:02 +00:00			# By adding an `i386` to the name the Omnibus cookbook's `load-omnibus-toolchain.bat`
			`# will load the 32-bit version of the MinGW toolchain.`
			`<% [ '', '-i386' ].each do \|win_suffix\| %>`
			`- name: windows-2012r2-standard<%= win_suffix %>`
			`driver:`
			`box: chef/windows-server-2012r2-standard # private`
			`synced_folders:`
			`# We have to mount this repos enclosing folder as the Omnibus build`
			`# gets cranky if the mounted source folder is a symlink. This`
			# mounts at `C:\vagrant\code` and the inspec source folder is available
			# at `C:\vagrant\code\inspec`
			`- ['../..', '/vagrant/code']`
			`provisioner:`
			`attributes:`
			`omnibus:`
			`build_user: vagrant`
			`build_user_group: Administrators`
			`build_user_password: vagrant`
			`install_dir: /opscode/inspec`
			`<% end %>`
add omnibus for inspec 2016-04-18 03:30:50 +00:00
			`suites:`
Improve windows support of omnibus installer - fix #889 2016-08-08 17:41:02 +00:00			`- name: inspec`
add omnibus for inspec 2016-04-18 03:30:50 +00:00			`run_list: omnibus::default`