# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#10 | 15837 | tjuricek | Removed HVEProjectsService, moved methods to module of projects app | ||
#9 | 15828 | tjuricek |
Remove 'service object' abstraction for helix sync, revise to module code. This begins removing an unnecessary level of indirection. As it turns out, the Helix Sync logic will remain largely untouched between different systems. If we need very specific logic, we'll have to adjust each method, likely with configuration. Which will of course need some testing, or just outright replacement, which *should* be easier with module includes. |
||
#8 | 15824 | tjuricek |
Fixes to the 'preview' or 'shelf resolve plan'. There's something fundamentally off about the shelf preview and resolve mechanism, I'm still investigating. Until that point, obvious flaws should be cleared up. |
||
#7 | 15821 | tjuricek | Clean up diagnostic information. | ||
#6 | 15787 | tjuricek | Added 'readd' test for Helix Sync submit | ||
#5 | 15786 | tjuricek |
Add 'remove from shelf' resolution test (with bug fixes). Also, removed a couple of old tasks from the top-level Rakefile. |
||
#4 | 15773 | tjuricek |
Add basic 'add' test for the submit shelf mechanism. Added a *slightly* modified deviceSync script, which ideally functions somewhat like the helix sync script. We'll start with this to generate our JSON examples for testing. |
||
#3 | 15761 | tjuricek |
Naive implementation of the "preview resolve plan". The API needs to be avaiable for the integration effort between Helix Cloud and Helix Sync. Tests to follow. |
||
#2 | 15757 | tjuricek |
Add resolve implementation for submitting from shelves for Helix Sync Includes additional concepts for creating a "helix sync shelf client" vs a "helix sync device client". It's expected that there's basically one shelf client per user per project. The "device" client is an additional client per user per project per machine. The HWS services will submit via the "shelf client". The resolve implementation remains untested at the moment in order to get the client changes in the hands of Helix Sync developers. |
||
#1 | 15622 | tjuricek |
Move source code to 'source/' subdirectory of branch. build/ will remain where it is. |
||
//guest/perforce_software/helix-web-services/main/helix_web_services/lib/helix_versioning_engine/hve_projects_service.rb | |||||
#5 | 15542 | tjuricek |
Add spaces to our basic 'component encode' mechanism, and use it for HVE project IDs. In general, this will make the HVE IDs a bit more readable. |
||
#4 | 15497 | tjuricek | Add support to fetch the latest change of a project. | ||
#3 | 15496 | tjuricek |
Revise GET /helix_sync/v1/changes/[project] to /helix_sync/v1/changes/[project]/pending The base method is really intended for the latest changelist number. Meh. |
||
#2 | 15487 | tjuricek | Add basic ability to create pending changelists for helix sync projects. | ||
#1 | 15479 | tjuricek | Added a basic "HVE project" implementation for creating clients. | ||
//guest/perforce_software/helix-web-services/main/helix_web_services/lib/projects/hve_projects.rb | |||||
#1 | 15437 | tjuricek |
Basic "HVE Project" implementation. This will allow directories in a HVE instance to host 'projects' for use by helix sync. There are no methods defined for creating the projects, however. This does not include any specialization or testing in the Qt API yet. I may investigate creating a "higher level" interface for Qt client apps. |