helix_versioning_engine.rb #2

# Copyright (c) 2015 Perforce Software, Inc.  All rights reserved.
require 'helix_versioning_engine/app'

module HelixVersioningEngine

  # p4d doesn't return empty results on user '-o' commands, it returns results
  # where the email address is set to 'user@INVALID'
  def self.invalid_user_email?(results, user)
    results.any? do |h|
      h['Email'] == "#{user}@INVALID"
    end
  end
  
end

#	Change	User	Description
#2	16114	Doug Scheirer	Merge from main
#1	15688	Doug Scheirer	Populate -o //guest/perforce_software/helix-web-services/... //guest/doug_scheirer/helix-web-services/....
//guest/perforce_software/helix-web-services/main/source/helix_web_services/lib/helix_versioning_engine.rb
#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/lib/helix_versioning_engine.rb
#3	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.
#2	15185	tjuricek	Update user spec management implementation, tests, and documentation.
#1	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.
//guest/perforce_software/helix-web-services/main/helix_web_services/lib/perforce.rb
#2	13839	tjuricek	Conversion of the p4_project_service microservice to new monolithic system. This may not have an HTTP front end in the monolithic system. Project services are really just about how the core object model is structured. It's likely that each application will add their own wrinkles and extensions to the system, so it's unlikely we'll need a generic "project model". Exactly how extensions are registered and used is still a bit TBD at the moment. Previously they were to be registered webhooks, that model may change. Does not include tests yet.
#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.
//guest/perforce_software/helix-web-services/main/p4_web_api/p4_web_api/lib/p4_web_api.rb
#4	13528	tjuricek	Moved rack and app server configuration to be managed via Salt. Also, only using a single value "url" to configure how the p4_project_services instance references the p4_web_api. And, removing the Docker setup, since that won't work for a production system.
#3	13481	tjuricek	Tests for the p4 web api and p4 project services now pass against a development setup both in and out of the docker cluster. Note that configuration has not been finalized, so conventions to dealing with development vs production need to be organized a bit.
#2	13439	tjuricek	Added a very trivial logIn implementation. This just makes the current POST request to /p4_phoenix_services/v1/sessions, which does not include the ability to create a host locked P4 ticket for the user. So it's not quite usable yet. But, I've made several tweaks to the API which should be stablizing.
#1	13412	tjuricek	Initial version of the web-services mainline. This is a collection of several projects, that will likely often get released together, though many of them may not always be relevant. See the README for more information.