Rakefile #1

require 'bundler/gem_tasks'

begin
  require 'rspec/core/rake_task'
  RSpec::Core::RakeTask.new(:spec) do |spec|
    spec.rspec_opts = "--format html --out #{File.absolute_path('../spec-output/helix_web_services_client_specs.html', __FILE__)}"
  end
rescue LoadError
end

begin
  require 'yard'
  YARD::Rake::YardocTask.new do |t|
    t.files = ['lib/**/*']
    t.options = ['-o', File.absolute_path('../doc-output', __FILE__),
      '-m', 'markdown']
  end
rescue LoadError
end

#	Change	User	Description
#1	15741	ptomiak	Branch HWS for my use.
//guest/perforce_software/helix-web-services/main/source/helix_web_services_client/Rakefile
#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/Rakefile
#7	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.
#6	15617	tjuricek	Add P4PORT variable to 'remotetest' task, add 'debug' option to client.
#5	15589	tjuricek	Update path to test output and update docs.
#4	15588	tjuricek	Write test output to build directory and correct reference to 'all:doc' task
#3	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.
#2	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.
#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.