Prepares a machine to be an Omnibus builder.
This project is managed by the CHEF Release Engineering team. For more information on the Release Engineering team's contribution, triage, and release process, please consult the CHEF Release Engineering OSS Management Guide.
Starting with omnibus cookbook version 4.0.0:
- Chef 11 is no longer supported, since 12.5.1 is required to use chef-ingredient. If needed, you can pin to omnibus version
3.2.xto preserve the old functionality.
- Instead of compiling everything from source in this cookbook, the omnibus-toolchain package will be installed. This package contains patch, bash, make, git, ruby, rubygems, and bundler (built from omnibus-software definitions).
This cookbook requires Chef 12.5.1+.
For a full list of supported platforms and external cookbook requirements, please see the
metadata.rb file at the root of the cookbook.
The default recipe is the main entrypoint for the cookbook and does the following:
- Ensures all required Omnibus-related directories are created and owned by the build user.
- Ensures a sane build tool-chain is installed and configured (using the build-essential cookbook)
- Ensures the necessary tools to run an Omnibus project (ruby, git, etc) are installed (using the omnibus-toolchain package)
- Includes a platform-specific recipe to apply additional tweaks as appropriate.
All other recipes should be treated as "private" and are not meant to be used individually. They only exist to support the
||The user to execute Omnibus builds as|
||The "base" directory where Omnibus will store its data.|
This resource is used to execute a build of an Omnibus project.
||The name of the Omnibus project to build|
||The directory to install Omnibus|
||The installation of the project being built|
||The base directory for Omnibus|
||Log level used during the build. Valid values include:
||Omnibus configuration file used for the build.|
||Overrides for one or more Omnibus config options|
||Indicates the Omnibus cache (including git cache) should be wiped before building.|
||The user to execute the Omnibus build as.|
||Environment variables to set in the underlying build process.|
||Indicates output of build process should be logged to Chef event stream.|
omnibus_build 'harmony' do project\_dir 'https://github.com/chef/omnibus-harmony.git' log_level :internal config_override( append_timestamp: true ) end
omnibus::default recipe in your node's run list and override the cookbook's default attributes as desired. At the very least you will want to override
node['omnibus']['install_dir'] to match the installation directory of your Omnibus project.
Using Test Kitchen with Docker
The following assumes you are on a Mac OS X workstation and have installed and started Kitematic.
- Set environment variables to point kitchen-docker at your local Kitematic instance:
export DOCKER_HOST=tcp://192.168.99.100:2376 export DOCKER_CERT_PATH=$HOME/.docker/machine/certs export DOCKER_TLS_VERIFY=1
set -gx DOCKER_HOST "tcp://192.168.99.100:2376" set -gx DOCKER_CERT_PATH "$HOME/.docker/machine/certs" set -gx DOCKER_TLS_VERIFY 1
- Run Test Kitchen with the provided .kitchen.docker.yml:
KITCHEN_LOCAL_YAML=.kitchen.docker.yml kitchen verify languages-ruby-ubuntu-1204
License & Authors
- Author: Seth Vargo (email@example.com)
- Author: Yvonne Lam (firstname.lastname@example.org)
- Author: Seth Chisamore (email@example.com)
- Author: Stephen Delano (firstname.lastname@example.org)
Copyright:: 2012-2016, Chef Software, Inc. (<email@example.com>) Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.