| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #2 | 15791 | tjuricek | Removing very old p4ws branch | ||
| #1 | 13266 | tjuricek |
Reorganized depot to avoid stream/main in path. This may be re-imported. |
||
| //guest/tjuricek/p4ws/stream/main/salt/srv/perforce/web-services/p4_project_services/deps.sls | |||||
| #7 | 13262 | tjuricek | Added the 'eval' Vagrant box that uses our deployed packages. | ||
| #6 | 13254 | 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 |
||
| #5 | 13237 | tjuricek |
Added a basic p4-project-services .deb package There is some kind of configuration issue with the production config that causes tests to fail. The service is running, however, so this is likely related to having a few things not managed via salt. |
||
| #4 | 13236 | tjuricek | Make sure that the p4 project services instance comes up after the libpq-dev package is installed. | ||
| #3 | 13235 | 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. |
||
| #2 | 13230 | 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 | 13225 | 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. |
||