Name | Modified | Size |
---|---|---|
.. | ||
errors | ||
app.rb | 9 years ago | |
change_service.rb | 9 years ago | |
client_service.rb | 9 years ago | |
methods.rb | 9 years ago |
Change | User | Description | Committed |
---|---|---|---|
17271 | tjuricek | Remove deprecated Ruby implementation. | 9 years ago |
17139 | tjuricek | Make sure we only include the JSON blob when we prepend a new human-readable description i...nstead of always prepending it to whatever's there. See P4WEBAPI-174 Allow our server to set the HVE_PROJECTS_PATH variable via the environment (to make it easier to test Helix Sync locally in an integrated manner). « |
9 years ago |
17136 | tjuricek | Serialize the syncConflict field. Revert change to nginx config - we do not want retrys... in the face of failure until we trust our recovery mechanism. « |
9 years ago |
17134 | tjuricek | Ensure there is no conflict detected if we have no head revision or our have revision matc...hes the head revision. « | 9 years ago |
17132 | tjuricek | Use our WORKSPACE_DIR as the root for temporary directories for Helix Sync operations. ... Slack request from dscheirer. « |
9 years ago |
17129 | tjuricek | Append an additional newline between the readable description, the JSON, and the delimiter.... « | 9 years ago |
17128 | tjuricek |
Add patchlevel check for 2014.2 servers. P4WEBAPI-169 |
9 years ago |
17126 | tjuricek | Don't update the description if the submittedChange key was not found. This is likely a... strange server response, so we just log what we actually saw. « |
9 years ago |
17125 | tjuricek | Only preserve the original description if it hasn't been specified already. | 9 years ago |
17124 | tjuricek | If a human readable description was added to a Helix Sync changelist before calling submit..., preserve it too. See: P4WEBAPI-165 « |
9 years ago |
17122 | tjuricek |
Add an optional human-readable description for submits via Helix Sync. P4WEBAPI-165 |
9 years ago |
17106 | tjuricek | When the user's action is delete, and the file is locked by another user, just the case as... another "remove" (ignore our changes). We either do that or fail the entire submit. « |
9 years ago |
17089 | tjuricek | Prefer handling removes first before handling locked files. If a file is deleted at hea...d (and we've deleted it), but someone has yet readded and locked the file, just treat the file as a remove. « |
9 years ago |
17061 | tjuricek | Return an empty array if there is no pending changelist to submit. Also, do not commit... the Version file if it exists. « |
9 years ago |
17040 | tjuricek | Remove block that set an error state if the return value was not an array with the first e...lement as a hash. In case the server decides to return an empty array, that's a valid successful value. I don't really have a nice way of testing this behavior though, since we don't get to this point if the plan is empty. « |
9 years ago |
17039 | tjuricek | Don't shift the submit results in case we have an empty array | 9 years ago |
17038 | tjuricek | Return the results of p4 submit when Helix Sync submit finishes. We *may* want to prese...rve the original plan and return that, but because this submit iterates and tweaks the plan as it goes, we probably want to start with just "ok what did you do". Also, set the '+w' flag on Gemfile.lock. I think that might make builds work. « |
9 years ago |
16280 | tjuricek | Adjustments for Helix Cloud settings Several tests are now disabled due for Helix Cloud... since they won't work on streams, which HC only uses. « |
9 years ago |
16190 | tjuricek | Implement methods for deleting shelf and device clients. | 9 years ago |
16189 | tjuricek | Implement delete for Helix Sync pending changelists on a project. | 9 years ago |
16167 | tjuricek | Use the '-x' flag on a specific client to obtain a "lock" before submitting files. Also... using the lock on typically generated temporary clients just in case. « |
9 years ago |
16106 | tjuricek | Revise the URLs for Helix Sync client workspaces. Added *stubs* for deleting the client...s for a user, implementations will follow. « |
9 years ago |
16103 | tjuricek | Revision of helix sync 'changelist' methods. | 9 years ago |
16102 | tjuricek | Rename GET /helix-sync/v1/changes/[project] -> GET /helix-sync/v1/[project]/last-change | 9 years ago |
16097 | tjuricek | Remove POST /helix-sync/v1/changes/[project] This will be handled by the Helix Sync cli...ent. « |
9 years ago |
16096 | tjuricek | Rename '/helix_sync' URLs to '/helix-sync' | 9 years ago |
16092 | tjuricek | The 'fetch latest' changelist now depends upon the shelve client existing for the request.... This may not be an obvious dependency. « |
9 years ago |
16091 | tjuricek | Alter Helix Sync client options and the 'latest pending changelist' query (via Alan Teague...) The 'fetch pending changelist' method now requires that the changelist have the 'shelved' status. This is generally appropriate, but requires a bit more client usage, to make simple unit tests... kind of annoying actually. Since this function is used by some of the other Helix Sync workflow tests, I've just removed the smaller tests. « |
9 years ago |
16072 | tjuricek | Helix Cloud integration for Helix Sync services. This includes a "mock_raymond" rails a...pplication for keeping tabs on basic integration with Helix Cloud. We do not test against a live server. See integration history for more details. « |
9 years ago |
15992 | tjuricek | Add default parameter option to getting the pending changelist for a Helix Sync project. ... This allows clients that treat HTTP errors as networking errors to not receive a 404 if the changelist doesn't exist. « |
9 years ago |
15885 | tjuricek | Helix Sync submit from shelf now renames files locked by other users. | 9 years ago |
15846 | tjuricek | When a file is locked during the Helix Sync submit, we skip that file in the plan. | 9 years ago |
15837 | tjuricek | Removed HVEProjectsService, moved methods to module of projects app | 9 years ago |
15835 | tjuricek | Use a special if-switch to determine the type of client to make, preserve older 404 behavi...or « | 9 years ago |
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. « |
9 years ago |
15824 | tjuricek | Fixes to the 'preview' or 'shelf resolve plan'. There's something fundamentally off abo...ut the shelf preview and resolve mechanism, I'm still investigating. Until that point, obvious flaws should be cleared up. « |
9 years ago |
15773 | tjuricek | Add basic 'add' test for the submit shelf mechanism. Added a *slightly* modified device...Sync script, which ideally functions somewhat like the helix sync script. We'll start with this to generate our JSON examples for testing. « |
10 years ago |
15761 | tjuricek | Naive implementation of the "preview resolve plan". The API needs to be avaiable for th...e integration effort between Helix Cloud and Helix Sync. Tests to follow. « |
10 years ago |
15757 | tjuricek | Add resolve implementation for submitting from shelves for Helix Sync Includes addition...al 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. « |
10 years ago |
15622 | tjuricek |
Move source code to 'source/' subdirectory of branch. build/ will remain where it is. |
10 years ago |