test.rb #2

  • //
  • guest/
  • perforce_software/
  • helix-web-services/
  • candidate/
  • source/
  • data/
  • p4init/
  • test.rb
  • Commits
# Change User Description Committed
#2 16345 tjuricek Removing candidate branch
#1 16342 tjuricek Create candidate branch.

This branch is mostly here to start work on our release infrastructure.
//guest/perforce_software/helix-web-services/main/source/data/p4init/test.rb
#5 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.
#4 15989 tjuricek Test changes needed for integrated Git Fusion testing.

Do not run p4init during 'remotetest' task to allow for reconfiguration after initialization.

Tweak the test data initialization to let the GF install handle depot initialization.
#3 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)
#2 15837 tjuricek Removed HVEProjectsService, moved methods to module of projects app
#1 15718 tjuricek Moving the test data initialization scripts to data/
//guest/perforce_software/helix-web-services/main/source/helix_web_services_client/p4init/test.rb
#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/p4init/test.rb
#8 15578 tjuricek Removing QSettings* usage from hws::Client.

The way QSettings was being used only is relevant for one connection at a time, and, it didn't seem to work on windows nicely anyway.
#7 15144 tjuricek Setup stream spec tests and documentation.

Also revised the documentation folder http_p4_web_api -> helix_versioning_engine
#6 15110 tjuricek Revise changes methods for new p4 connection handling, add server specs, remove model references in client, and update asciidoc documentation.
#5 14893 tjuricek Add an alternative test data setup that should work against the installed package server.

Unlike the local p4d instance, the installer configuration already creates the super user and depots, and sets the system security, etc. We just need to seed the additional users.
#4 13941 tjuricek Re-implemented the sync project methods at the HTTP level.

The Qt API is missing the "members" concept, but it's likely not quite usable just yet. It's existing logic does work, however.
#3 13939 tjuricek First pass at sync project service.

Includes a first pass at validating projects enabled for Sync. (There's only one branch check at the moment.)

Does not include the HTTP layer.
#2 13846 tjuricek Setup development rules for creating/initializing PostgreSQL, and updated some of the ProjectService specs.
#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.