| Change | User | Description | Committed |
|---|---|---|---|
| 15622 | tjuricek |
Move source code to 'source/' subdirectory of branch. build/ will remain where it is. |
10 years ago |
| 15578 | tjuricek | Removing QSettings* usage from hws::Client. The way QSettings was being used only is re...levant for one connection at a time, and, it didn't seem to work on windows nicely anyway. « |
10 years ago |
| 15144 | tjuricek | Setup stream spec tests and documentation. Also revised the documentation folder http_p...4_web_api -> helix_versioning_engine « |
10 years ago |
| 15110 | tjuricek | Revise changes methods for new p4 connection handling, add server specs, remove model refe...rences in client, and update asciidoc documentation. « | 10 years ago |
| 14893 | tjuricek | Add an alternative test data setup that should work against the installed package server. ... Unlike the local p4d instance, the installer configuration already creates the super user and depots, and sets the system security, etc. We just need to seed the additional users. « |
10 years ago |
| 13941 | tjuricek | Re-implemented the sync project methods at the HTTP level. The Qt API is missing the "m...embers" concept, but it's likely not quite usable just yet. It's existing logic does work, however. « |
10 years ago |
| 13939 | tjuricek | First pass at sync project service. Includes a first pass at validating projects enable...d for Sync. (There's only one branch check at the moment.) Does not include the HTTP layer. « |
10 years ago |
| 13846 | tjuricek | Setup development rules for creating/initializing PostgreSQL, and updated some of the Proj...ectService specs. « | 10 years ago |
| 13799 | tjuricek | Start with branch specs hosting in a new monolithic 'helix web services' project. Conve...rting from a microservice to a monolithic architecture due to resource constraints at getting a deployable system running. Additionally, since it's not expected that people will upgrade often, the major benefit of microservices - being able to add services individually without affecting others - is not really a major benefit. The Ruby SDK will be consolidated into a single 'helix web services client' project. It may end up being distributed via Rubygems. This only runs branch specs at the moment. I want to get a CD pipeline setup for the monolithic server before revising more methods. « |
10 years ago |