helix_web_services_client.gemspec #2

  • //
  • guest/
  • perforce_software/
  • helix-web-services/
  • main/
  • source/
  • ruby_client/
  • helix_web_services_client.gemspec
  • Commits
# Change User Description Committed
#2 18626 tjuricek Create first spec with swagger-based Ruby client.
Remove older ruby infrastructure.
#1 17275 tjuricek Rename directory to "ruby_client" to avoid confusion.
//guest/perforce_software/helix-web-services/main/source/helix_web_services_client/helix_web_services_client.gemspec
#2 15969 tjuricek Add support for repo creation/update and deletion, same for SSH keys.

Add util module for supporting methods, modify temp client to dissapear.

(Modified submit of review 15549 by @ptomiak)
#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_client/helix_web_services_client.gemspec
#3 15132 tjuricek Provde a basic submit -e mechanism on classic perforce workspaces.
#2 15032 tjuricek Starting config and doc revisions.
System is now broken while revisions underway.

Configuration of the p4d connection is now done via a single HWSSettings middleware object injected into the Rack env.

The HWSP4Cleanup middleware now cleans up any p4 injected into the Rack env.

The Auth::App class now mostly just contains one method to generate a p4 ticket. /auth/v1/login.

Added yard documentation for the main project.

Yard docs have been reconfigured to dump into build/ directories. This should probably be done with each release. Hm...

The top level rake file contains a task, 'all:doc', to update our documentation. This should probably be run for each checkin. Hm...

Specs are now using Rack::Test on top of a 'live' p4d. I'd suggest you still use the p4util mechanism, which now dumps to a /tmp folder, so we can safely add P4IGNORE rules back into your local .p4config file.

Old 'perforce' application now called 'helix_versioning_engine'.

Removing cache data. Helix Sync may be slow. It may also get axed. We'll see.
#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.