# # Copyright 2015 YOUR NAME # # All Rights Reserved. # name 'p4_web_api' maintainer 'Tristan Juricek <tjuricek@perforce.com>' homepage 'https://perforce.com' install_dir "/opt/perforce/web-services/#{name}" build_version '2015.1.0' build_iteration 1 # Creates required build directories dependency 'preparation' # p4_web_api dependencies/components dependency 'p4_web_api-source' # Version manifest file dependency 'version-manifest' exclude '**/.git' exclude '**/bundler/git'
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#5 | 13972 | tjuricek |
Removing old microservice implementations. The system is now mostly a monolith. Eventually there will be a websocket service. |
||
#4 | 13544 | tjuricek |
Revise package and gem versioning. Packages will use [gem]-[changelist] as their versions. Gems will use a standard Ruby MAJOR.MINOR.REVISION format. P4WEBAPI-64 |
||
#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. |