| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #6 | 13525 | tjuricek |
Setup God to manage both the p4 web api and p4 project services processes. Apparently, there can only be one true god per machine. |
||
| #5 | 13515 | tjuricek |
Initial configuration for the p4_project_services. The tests haven't been run yet, so it's likely missing some more configuration. Using vagrant to even manage these environments may not be our realistic CD premise. I may end up moving some more responsibility into the Salt layer, which would make vSphere automation easier. |
||
| #4 | 13512 | tjuricek |
Add 'test-ubuntu12' environment that sets up projects based on "production" packages. Packages are installed from source files that should have been created by the last 'build-ubuntu12' environment. Since the package building process "dirties" up the environment it's better to use a clean system to test package installation. |
||
| #3 | 13496 | tjuricek |
Complete and seed the setup of the p4webapi in a development mode. This works against the local development tree for dev environments. |
||
| #2 | 13495 | tjuricek |
Basic p4d configuration for development/evaluation. Uses the perforce-server package and just triggers the creation of the helix-evaluation server "instance". This should nicely just ignore the default setup in case these scripts are used in the Helix OVA appliance setup. |
||
| #1 | 13494 | tjuricek | Reorganize salt tree to have a single set of states (probably) organized with different basic minion configurations. |