# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#6 | 15622 | tjuricek |
Move source code to 'source/' subdirectory of branch. build/ will remain where it is. |
||
#5 | 15147 | tjuricek |
Enable submissions by files on stream clients This obeys our earlier rules: notably the local client must not have any local files open for edit. |
||
#4 | 15142 | tjuricek |
Use the super permission to clean up clients used in tests. For whatever reason, when I was testing this using a localhost connection, I never ran into this issue. Might be special rules to avoid permission checks locally? |
||
#3 | 15133 | tjuricek | Fix case to require 'P4' statement: "require 'p4'" only works on a case-insensitive system. | ||
#2 | 15132 | tjuricek | Provde a basic submit -e mechanism on classic perforce workspaces. | ||
#1 | 15059 | tjuricek | Tested authentication of the core /auth/v1/login method. | ||
//guest/perforce_software/helix-web-services/main/helix_web_services_client/spec/test_connections.rb | |||||
#4 | 15053 | tjuricek |
Revise the client API to use the new login method. The current specs will need to be revised since data normalization is moving out of the server and into the client. |
||
#3 | 14899 | tjuricek | Do not verify SSL certs in tests, and make sure the right DB file is used by our startup script. | ||
#2 | 14898 | tjuricek |
Specify the entire host string when executing tests against a remote host. The new package sets up vs a self-signed cert, so now we can watch failures over SSL. |
||
#1 | 13799 | tjuricek |
Start with branch specs hosting in a new monolithic 'helix web services' project. Converting 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. |