| Name | Modified | Size |
|---|---|---|
| .. | ||
| errors | ||
| helix_web_services_client | ||
| errors.rb | 10 years ago | |
| helix_web_services_client.rb | 10 years ago |
| Change | User | Description | Committed |
|---|---|---|---|
| 15622 | tjuricek |
Move source code to 'source/' subdirectory of branch. build/ will remain where it is. |
10 years ago |
| 15617 | tjuricek | Add P4PORT variable to 'remotetest' task, add 'debug' option to client. | 10 years ago |
| 15517 | tjuricek | Do not require changelist ID for submitting Helix Sync pending changelists. | 10 years ago |
| 15499 | tjuricek | Naive implementation of helix sync project submit for "helix versioning engine projects". | 10 years ago |
| 15497 | tjuricek | Add support to fetch the latest change of a project. | 10 years ago |
| 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. « |
10 years ago |
| 15487 | tjuricek | Add basic ability to create pending changelists for helix sync projects. | 10 years ago |
| 15479 | tjuricek | Added a basic "HVE project" implementation for creating clients. | 10 years ago |
| 15461 | tjuricek | Allow the settings to be specified on initialization of the client, and deal with Nginx is...sues and header keys. Nginx, by default, blocks all headers with underscores. Rack, on the other hand, convert hyphens to underscores. « |
10 years ago |
| 15437 | tjuricek | Basic "HVE Project" implementation. This will allow directories in a HVE instance to ho...st '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. « |
10 years ago |
| 15297 | tjuricek | Implement of 'cluster services' configuration. The configuration will be stored in a lo...cal JSON file, which is expected to be maintained by the systems admin. Eventually, it's expected to have this sort of thing implemented via Helix Admin. « |
10 years ago |
| 15240 | tjuricek | Set api level via request path on all Helix Versioning Engine methods. This will allow... migration of applications to different P4D versions. Our internal methods (like project API) should attempt to handle backward compatibility similarly. P4WEBAPI-118 « |
10 years ago |
| 15228 | tjuricek | Revise triggers implementation, tests, and documentation. | 10 years ago |
| 15227 | tjuricek | Revise implementation, tests, and documentation for protections management. Remove some... specs I will not be revising from the helix_web_services project. « |
10 years ago |
| 15225 | tjuricek | Revise counter implementation, tests, and documentation Wasn't available in the Ruby cl...ient before, so, it's now available. « |
10 years ago |
| 15222 | tjuricek | Revise server specs testing and documentation. Note: also fixed issues with setting P4P...ORT via headers. For whatever reason, the host setting doesn't seem to work like I expect it to, though P4PORT works just fine. « |
10 years ago |
| 15211 | tjuricek | Implement tests and documentation for label spec management. | 10 years ago |
| 15210 | tjuricek | Implement tests and documentation for job spec management. | 10 years ago |
| 15209 | tjuricek | Implement tests and documentation for group spec management. | 10 years ago |
| 15208 | tjuricek | Revise 'command' implementation, tests, and documentaiton. This includes a change from... a command blacklist to a whitelist. See P4WEBAPI-21 « |
10 years ago |
| 15205 | tjuricek | Implemented tests and documentation for depot spec editing. | 10 years ago |
| 15189 | tjuricek | Update files implementation, testing, and documentation. | 10 years ago |
| 15185 | tjuricek | Update user spec management implementation, tests, and documentation. | 10 years ago |
| 15132 | tjuricek | Provde a basic submit -e mechanism on classic perforce workspaces. | 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 |
| 15099 | tjuricek | Revise project services to be our simple 'container' for other systems. | 10 years ago |
| 15098 | tjuricek | Revised project services to GET-only forms. With Helix Sync revising to integrate purel...y with Helix Cloud, this is the only thing we can reasonably define. « |
10 years ago |
| 15090 | tjuricek | Update _proposed_ API for project services. This is *very likely* to change, and will n...ot be implemented until reviewed. « |
10 years ago |
| 15078 | tjuricek |
clients spec method revisions Updated some other documentation. |
10 years ago |
| 15077 | tjuricek | Add new 'model' technique, revised branch spec operations, test Auth::Middleware. The R...uby client now does *not* strictly type anything, but extends OpenStruct with helper methods to help deal with inconsistent data formats. See the OpenModel class documentation for more details. The Auth::Middleware class is also *finally* implemented as well. This does not take into account all possible variations of server behavior (yet), but that will happen in follow-up work. « |
10 years ago |
| 15059 | tjuricek | Tested authentication of the core /auth/v1/login method. | 10 years ago |
| 15053 | tjuricek | Revise the client API to use the new login method. The current specs will need to be re...vised since data normalization is moving out of the server and into the client. « |
10 years ago |
| 15038 | tjuricek | Document 'login' auth method and client programming overview. | 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 |
| 13891 | tjuricek | Added a 'member' concept to projects. members is the start of a basic project 'role' de...finition. In Helix sync, this is mostly just used to indicate this is a "my Project" in the UI and a project member can have the ability to leave the project or add someone else. Eventually, we expect "members" to mean more, like, is part of a group that has write access to the files of the project. But that sort of definition is very TBD. « |
10 years ago |
| 13884 | tjuricek | Add Project extension classes models, and the ability for the Project to handle before- an...d after- create callbacks to other services. « | 10 years ago |
| 13847 | tjuricek | Implement model conversion from the cache data project definitions, which gets basic CRU m...ethods functioning in the converted ProjectService « | 10 years ago |
| 13846 | tjuricek | Setup development rules for creating/initializing PostgreSQL, and updated some of the Proj...ectService specs. « | 10 years ago |
| 13839 | tjuricek | Conversion of the p4_project_service microservice to new monolithic system. This may no...t have an HTTP front end in the monolithic system. Project services are really just about how the core object model is structured. It's likely that each application will add their own wrinkles and extensions to the system, so it's unlikely we'll need a generic "project model". Exactly how extensions are registered and used is still a bit TBD at the moment. Previously they were to be registered webhooks, that model may change. Does not include tests yet. « |
10 years ago |
| 13808 | tjuricek | Finish converting most of the core p4d API into the new monolithic system. | 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 |