# Ignore RubyMine files .idea # Any directory named 'work' is typically used for downloaded p4d, and # p4droots setup by ruby utilities work # We'll use this as our default 'local bundler cache' which we use to actually # create packages that include all their very own gem dependencies. vendor/cache # The output of most build commands goes in pkg pkg # Temporary files created by the docbook generation stuff *.pyc # We use this output directory for specs so that Jenkins can collate the output spec-output # Temporary output of the yardoc (Ruby documentation) tasks .yardoc doc-output # Oh, thank you Apple .DS_Store .vagrant # Ignore any package files that might have been put into the source directory perforce*.deb perforce*.changes # Working directories used by TestKitchen to generate Omnibus installers in VMs .kitchen # Need to make sure helper tools (like RubyMine) do not attempt to check this # in. .p4config # This is a file of versions of the different projects within web services along # with the configuration file, usable by the bash script. The version numbers # come from either the Ruby configuration, except for the changelist number, # which either comes from a p4 command or the environment. p4ws-versions.sh
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 15741 | ptomiak | Branch HWS for my use. | ||
//guest/perforce_software/helix-web-services/main/source/helix_web_services_client/.p4ignore | |||||
#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/.p4ignore | |||||
#3 | 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. |
||
#2 | 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". |
||
#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. |