driver: name: vagrant forward_agent: yes customize: cpus: 2 memory: 2048 synced_folders: - ['.', '/home/vagrant/p4_web_services_auth'] provisioner: name: chef_zero require_chef_omnibus: 11.16.4 platforms: - name: centos-7.0 run_list: yum-epel::default - name: centos-6.5 run_list: yum-epel::default - name: centos-5.10 run_list: yum-epel::default - name: debian-7.2.0 run_list: apt::default - name: debian-6.0.8 run_list: apt::default - name: freebsd-10.0 run_list: freebsd::portsnap - name: freebsd-9.2 run_list: - freebsd::portsnap - freebsd::pkgng - name: ubuntu-14.04 run_list: apt::default - name: ubuntu-12.04 run_list: apt::default - name: ubuntu-11.04 run_list: apt::default - name: ubuntu-10.04 run_list: apt::default suites: - name: default run_list: omnibus::default attributes: omnibus: build_user: vagrant build_user_group: vagrant build_user_password: vagrant install_dir: /opt/p4_web_services_auth
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#2 | 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. |
||
#1 | 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. |