| Name | Modified | Size |
|---|---|---|
| .. | ||
| omnibus-p4_web_services_auth |
| Change | User | Description | Committed |
|---|---|---|---|
| 13520 | tjuricek | Created a 'cluster' build procedure that creates an installer on build, and executes the i...nstall 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. « |
10 years ago |
| 13504 | tjuricek | The 'build-ubuntu12' seems to generate the appropriate debian packages for the distributio...n. I had permissions issues (probably related to shared folder usage) with the dpkg tools. So I've removed them. If we happen to need them, we'll have to figure out a build process. This environment probably shouldn't be used to test the packages, since omnibus likes to dirty everything up, leave files in the /opt/perforce directory owned by vagrant, etc. « |
10 years ago |
| 13500 | tjuricek | Reorganizing Vagrant definitions. Each platform should allow developers to launch envir...onments 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. « |
10 years ago |