| # | 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/helix_web_services_client/Gemfile.lock | |||||
| #5 | 15971 | tjuricek | Add git_fusion_strings to source tarball | ||
| #4 | 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) |
||
| #3 | 15719 | tjuricek | Ensuring the omnibus steps do not fail due to read-only access caused by the p4 client. | ||
| #2 | 15718 | tjuricek | Moving the test data initialization scripts to data/ | ||
| #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/Gemfile.lock | |||||
| #5 | 15132 | tjuricek | Provde a basic submit -e mechanism on classic perforce workspaces. | ||
| #4 | 15121 | tjuricek | Update p4util dependency (fix for login -p usage that breaks current test runs vs package pipeline) | ||
| #3 | 15120 | tjuricek |
Updating gem dependencies. p4util required updating might as well update others, seems to work. |
||
| #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 | 14794 | tjuricek |
Omnibus installation framework. Right now, this mostly just packages up most of the software for use within an embedded ruby distribution. Not everything is working because there are decisions to make I'm not entirely sure about. Things, like, "do we embed postgres", or "do I embed unicorn and generate a stupid init.d script". |
||