source 'https://rubygems.org' # Install omnibus gem 'omnibus', github: 'chef/omnibus' # 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' # 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', '~> 3.0' # Use Test Kitchen with Vagrant for converging the build environment gem 'test-kitchen', '~> 1.2' gem 'kitchen-vagrant', '~> 0.14' end
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#4 | 18235 | tjuricek | Remove old omnibus packaging logic. | ||
#3 | 17093 | tjuricek |
Removed omnibus-software dependencies, in preparing for license compliance. This removes our external dependency on the omnibus-software project in Gitlab. To make it easier to maintain license compliance for compiled libraries, the omnibus software configurations will be edited to copy appropriate LICENSE files into the distributed packages. |
||
#2 | 17058 | tjuricek |
Alter omnibus build to meet our current naming conventions. The strange bit here is that the 'build_iteration' includes the architecture name on debian, but on rpms, we generate it in the omnibus level. This may confuse people. See also: https://confluence.perforce.com:8443/display/IP/Package+Naming+Approach#PackageNamingApproach-LinuxPackageNamingApproach |
||
#1 | 15622 | tjuricek |
Move source code to 'source/' subdirectory of branch. build/ will remain where it is. |
||
//guest/perforce_software/helix-web-services/main/packaging/omnibus-helix-web-services/Gemfile | |||||
#1 | 14794 | tjuricek |
Omnibus installation framework. Right now, this mostly just packages up most of the software for use within an embedded ruby distribution. Not everything is working because there are decisions to make I'm not entirely sure about. Things, like, "do we embed postgres", or "do I embed unicorn and generate a stupid init.d script". |