- #!/usr/bin/env ruby
- require "bundler/setup"
- require "helix_web_services_client"
- # You can add fixtures and/or initialization code here to make experimenting
- # with your gem easier. You can also use a different console, if you like.
- # (If you use this, don't forget to add pry to your Gemfile!)
- # require "pry"
- # Pry.start
- require "irb"
- IRB.start
| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #1 | 15688 | Doug Scheirer | Populate -o //guest/perforce_software/helix-web-services/... //guest/doug_scheirer/helix-...web-services/.... « |
10 years ago | |
| //guest/perforce_software/helix-web-services/main/source/helix_web_services_client/bin/console | |||||
| #1 | 15622 | tjuricek |
Move source code to 'source/' subdirectory of branch. build/ will remain where it is. |
10 years ago | |
| //guest/perforce_software/helix-web-services/main/helix_web_services_client/bin/console | |||||
| #1 | 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 | |