source 'https://rubygems.org' # Install omnibus gem 'omnibus', '~> 4.0' # 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: 'opscode/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 #gemspec :path => '../p4_web_api', :name => 'p4_web_api'
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#4 | 13972 | tjuricek |
Removing old microservice implementations. The system is now mostly a monolith. Eventually there will be a websocket service. |
||
#3 | 13520 | tjuricek |
Created a 'cluster' build procedure that creates an installer on build, and executes the install on a test instance. The main change is to package all gem dependencies via 'vendor/cache' (using the 'bundle package' command). Right now, there appears to be an issue with test data initialization, which may need a revised approach. |
||
#2 | 13500 | tjuricek |
Reorganizing Vagrant definitions. Each platform should allow developers to launch environments for development, builds, or 'production', so the entire CD process can be evaluated by anyone wiht access to the source tree. This may eventually bring up a transient vSphere machine up and down, which may be necessary for sandboxing Omnibus related builds. |
||
#1 | 13499 | tjuricek |
Simple p4_web_api omnibus installer. Successfully built using a test-kitchen VM for debian ubuntu 14.04. |