| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #12 | 15622 | tjuricek |
Move source code to 'source/' subdirectory of branch. build/ will remain where it is. |
||
| #11 | 15618 | tjuricek |
By default, writing spec results to spec-output, docs to doc-output. The archiving in a 'build' branch will be handled by the CD pipeline. |
||
| #10 | 15589 | tjuricek | Update path to test output and update docs. | ||
| #9 | 15588 | tjuricek | Write test output to build directory and correct reference to 'all:doc' task | ||
| #8 | 15513 | tjuricek |
Add a product ID header for debugging purposes. This will generally display INVALID unless the version file has been created during the build. |
||
| #7 | 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. |
||
| #6 | 14841 | tjuricek |
Add *very basic* shell script wrappers to configure and launch the unicorn server. hws_configure: post-install script to setup or migrate the DB helix_web_services: bash script to point out the embedded Ruby setup This is far from complete, just the next step in getting to a basic package-based deployment. |
||
| #5 | 14192 | tjuricek |
Starting work on running tests via the command line again. The current system seems to run into problems with local .p4config settings. I'm investigating workarounds. We may need to move "working folders" into a location outside of this tree by default. |
||
| #4 | 14054 | tjuricek |
Allowing the Qt client to select 'all' vs 'my' projects. Right now, it should default to using "my" projects as a rule. |
||
| #3 | 13891 | tjuricek |
Added a 'member' concept to projects. members is the start of a basic project 'role' definition. In Helix sync, this is mostly just used to indicate this is a "my Project" in the UI and a project member can have the ability to leave the project or add someone else. Eventually, we expect "members" to mean more, like, is part of a group that has write access to the files of the project. But that sort of definition is very TBD. |
||
| #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. |