| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #38 | 18626 | tjuricek |
Create first spec with swagger-based Ruby client. Remove older ruby infrastructure. |
||
| #37 | 17144 | tjuricek |
Prepare build for java-land / Ignore trust settings for non-SSL connections. build.sh now depends upon java basically being correctly installed. (Java 8 JDK with JCE for p4 SSL connections.) |
||
| #36 | 17112 | tjuricek | Add the p4util local package to the tarball to enable testing | ||
| #35 | 17111 | tjuricek |
Add '-s' option to p4util start to enable a self-signed SSL mode. And, submit changes to the Gemfile.lock that may fix problems in the test environment. |
||
| #34 | 17110 | tjuricek | Copy p4util project just to make it easier to use in the build system. | ||
| #33 | 17091 | tjuricek | Fixing issue where asciidoc file was renamed to 'hws.doc' from obsolete id. | ||
| #32 | 17088 | tjuricek |
Fixing build.sh problems with release notes. The 'package' task seems to magically call my other rake tasks to copy files, which doesn't quite make sense. So guard those tasks by only copying if the file doesn't already exist. We get failures in the build since our clients are readonly by default. |
||
| #31 | 17087 | tjuricek | Moving release notes to the (codeline)/p4-doc/user directory. | ||
| #30 | 17084 | tjuricek |
Call 'rake Version' explicitly For whatever reason the Rake task dependency chain seems to call 'Version' after 'package' when running rake build. This actually seems somewhat inconsistent behavior, because it worked just fine in my environment. |
||
| #29 | 17083 | tjuricek | Add message related to copying the version file (if it exists) in the build | ||
| #28 | 17076 | tjuricek |
Allow the build to succeed if the Version file does not exist. This is an interim fix for Jenkins builds, mostly |
||
| #27 | 17072 | tjuricek |
Add encoding information from the Ruby interpreter. This may help us debug observed issues happening when running under EC automation. |
||
| #26 | 17059 | tjuricek | Include the Version file in the tarball, and use that file (if it exists) for the changelist during the package build. | ||
| #25 | 17058 | tjuricek |
Alter omnibus build to meet our current naming conventions. The strange bit here is that the 'build_iteration' includes the architecture name on debian, but on rpms, we generate it in the omnibus level. This may confuse people. See also: https://confluence.perforce.com:8443/display/IP/Package+Naming+Approach#PackageNamingApproach-LinuxPackageNamingApproach |
||
| #24 | 16328 | tjuricek | Fix default nginx reference in local development testing mode | ||
| #23 | 16327 | tjuricek |
Fix issue where 'rake remote:spec' did not correctly hit the remote HWS server Change the logic of the login spec. When the HWS is running on a different instance, we seem to get different login tickets. It's also completely random for cloud anyway. Wrap more of the deviceSync.rb output in a guard |
||
| #22 | 16322 | tjuricek | Fix reference and add 'tag' parameter to name the output file from the remote:spec task | ||
| #21 | 16321 | tjuricek | Data subdirectory glob needs the extra asterix | ||
| #20 | 16320 | tjuricek | Use absolute path to the data initialization directory, and make sure that information is included in the tarball. | ||
| #19 | 16316 | tjuricek | Add 'group' setting (which can be nulled) to set the privileges on the installed unicorn config | ||
| #18 | 16314 | tjuricek | Add default self-signed certs to tarball | ||
| #17 | 16311 | tjuricek |
Altering how the 'remote' tests are run, since we no longer distribute perforce-server with the installer. Removing the remote p4d init, which will not be used. |
||
| #16 | 16303 | tjuricek |
Add the ability to start up p4d in different configurations directly only. (Useful when just running things under a debugger.) |
||
| #15 | 16290 | tjuricek | Fix deployment changes with recent changes for Helix Cloud testing. | ||
| #14 | 16285 | tjuricek |
Deploy/install improvements - Include nginx in Omnibus distribution, do not conflict with system nginx install - Use old-school sysvinit scripts - Create 'hws_launch' wrapper to initiate nginx and unicorn, which also reads system config file for settings |
||
| #13 | 16204 | tjuricek | Added release notes, which show up in the tarball and installer product home directory | ||
| #12 | 16115 | tjuricek | Add methods to top-level rakefile to make it a little easier to start/top the cloud configuration (for development). | ||
| #11 | 16072 | tjuricek |
Helix Cloud integration for Helix Sync services. This includes a "mock_raymond" rails application for keeping tabs on basic integration with Helix Cloud. We do not test against a live server. See integration history for more details. |
||
| #10 | 15991 | tjuricek | Add contrib directory to source tarball. | ||
| #9 | 15989 | tjuricek |
Test changes needed for integrated Git Fusion testing. Do not run p4init during 'remotetest' task to allow for reconfiguration after initialization. Tweak the test data initialization to let the GF install handle depot initialization. |
||
| #8 | 15974 | tjuricek | Run remote tests in the context of bundler | ||
| #7 | 15971 | tjuricek | Add git_fusion_strings to source tarball | ||
| #6 | 15786 | tjuricek |
Add 'remove from shelf' resolution test (with bug fixes). Also, removed a couple of old tasks from the top-level Rakefile. |
||
| #5 | 15721 | tjuricek | Change default mode of Gemfile.lock right before packaging. | ||
| #4 | 15718 | tjuricek | Moving the test data initialization scripts to data/ | ||
| #3 | 15689 | tjuricek |
Remove README.md from source tarball. We can add another one later, but the prior README was really intended as a basic landing page for the workshop. |
||
| #2 | 15634 | tjuricek |
Add rules for setting up and running Centos 6. There's a strange problem coming back around with package tests again, not everything's 100% |
||
| #1 | 15622 | tjuricek |
Move source code to 'source/' subdirectory of branch. build/ will remain where it is. |
||
| //guest/perforce_software/helix-web-services/main/Rakefile | |||||
| #61 | 15619 | tjuricek | Remove all doc-output and spec-output dirs on clean task | ||
| #60 | 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. |
||
| #59 | 15617 | tjuricek | Add P4PORT variable to 'remotetest' task, add 'debug' option to client. | ||
| #58 | 15614 | tjuricek | Add 'remotetest' task to run the client API remotely (after seeding p4d) | ||
| #57 | 15591 | tjuricek | Do not rebuild documentation automatically (yet). | ||
| #56 | 15588 | tjuricek | Write test output to build directory and correct reference to 'all:doc' task | ||
| #55 | 15587 | tjuricek |
Add 'rake test' top level command to handle executing tests against the local source tree. This may be embellished with some additional configuration to, say, run tests against a remote server. |
||
| #54 | 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. |
||
| #53 | 15240 | tjuricek |
Set api level via request path on all Helix Versioning Engine methods. This will allow migration of applications to different P4D versions. Our internal methods (like project API) should attempt to handle backward compatibility similarly. P4WEBAPI-118 |
||
| #52 | 15090 | tjuricek |
Update _proposed_ API for project services. This is *very likely* to change, and will not be implemented until reviewed. |
||
| #51 | 15038 | tjuricek | Document 'login' auth method and client programming overview. | ||
| #50 | 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. |
||
| #49 | 14891 | tjuricek | Add packaging directory to source tarball. | ||
| #48 | 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. |
||
| #47 | 14054 | tjuricek |
Allowing the Qt client to select 'all' vs 'my' projects. Right now, it should default to using "my" projects as a rule. |
||
| #46 | 13974 | tjuricek |
Moving 'ui/static' to 'helix_web_components' project, and altering some notes. Also, removed obsolete top-level Rake tasks. The "Helix Web Components" project will likely get moved elsewhere in the future. |
||
| #45 | 13960 | tjuricek |
Setup a development config for nginx /hws points to the new monolithic helix_web_serivces instance / points to a static directory This static directory may end up getting moved around into other projects, I'm not sure where that location should be. |
||
| #44 | 13759 | tjuricek |
Fix the 'source' declaration that broke the installer build process. The 'perforce.rb' file. |
||
| #43 | 13707 | tjuricek |
Infrastructure for including a "project management" React application. This attempts to create a fairly simple installer that creates a 'static' folder based on ui/static that gets hosted by the nginx front end. Right now, it's the only app, so the default page is this application. It was called "pws2" during a prototyping phase. Another prototype, "pws" and the related "project" module, is removed since that was a Sinatra-based approach that will be much more difficult to integrate into anything else. I'm running into a couple of issues with notifications setup, it's still not 100%, so I'm disabling this for now from the default 'god' configuration. (The service isn't 100% functional yet, anyway.) |
||
| #42 | 13551 | tjuricek | Don't use a temp 'dist' folder and include the file extensions in the package manifests. | ||
| #41 | 13545 | tjuricek | Allow the environment to set the changelist, which is generally true in CI systems. | ||
| #40 | 13544 | tjuricek |
Revise package and gem versioning. Packages will use [gem]-[changelist] as their versions. Gems will use a standard Ruby MAJOR.MINOR.REVISION format. P4WEBAPI-64 |
||
| #39 | 13531 | tjuricek | Remove commented out rake tasks that have been superceded by Salt. | ||
| #38 | 13530 | tjuricek |
Add p4_phoenix_services package and Salt configuration for deployment. This uncovered a couple of issues from the C++ API during it's conversion to C++03. So, in a nutshell, most operations, except for notifications, appear to be working (well, using Vagrant machines). |
||
| #37 | 13527 | tjuricek |
Added a basic p4-project-services .deb package There is some kind of configuration issue with the production config that causes tests to fail. The service is running, however, so this is likely related to having a few things not managed via salt. |
||
| #36 | 13520 | tjuricek |
Created a 'cluster' build procedure that creates an installer on build, and executes the install on a test instance. The main change is to package all gem dependencies via 'vendor/cache' (using the 'bundle package' command). Right now, there appears to be an issue with test data initialization, which may need a revised approach. |
||
| #35 | 13519 | tjuricek |
Added a 'buildmaster' environment. The 'buildmaster' sets up Ruby locally for doing some work via Rake. Additional steps are now being figured out in the README.md, which may end up being a bash script that executes on the master. |
||
| #34 | 13513 | tjuricek | Update several files that were missing from the last commit regarding a basic 'test' environment | ||
| #33 | 13504 | tjuricek |
The 'build-ubuntu12' seems to generate the appropriate debian packages for the distribution. I had permissions issues (probably related to shared folder usage) with the dpkg tools. So I've removed them. If we happen to need them, we'll have to figure out a build process. This environment probably shouldn't be used to test the packages, since omnibus likes to dirty everything up, leave files in the /opt/perforce directory owned by vagrant, etc. |
||
| #32 | 13500 | tjuricek |
Reorganizing Vagrant definitions. Each platform should allow developers to launch environments for development, builds, or 'production', so the entire CD process can be evaluated by anyone wiht access to the source tree. This may eventually bring up a transient vSphere machine up and down, which may be necessary for sandboxing Omnibus related builds. |
||
| #31 | 13489 | tjuricek |
Add zookeeper service to cluster for development evaluation. It's a little unclear exactly what values need to be distributed via zk, since a lot of the configuration may end up being handled via ports. I wanted to at least provide a way to evaluate this. P4WEBAPI-60 |
||
| #30 | 13488 | tjuricek |
Added hsm:startworld and hsm:stopworld tasks to do global starts and stops. This is not without apparent issues. It appears bundler or ruby is pausing before the nginx launch task happens. I'm not sure if there's some kind of resource issue first. P4WEBAPI-49 |
||
| #29 | 13485 | tjuricek | Wrapping issues with setting up :test namespace and ignoring for now. | ||
| #28 | 13484 | tjuricek |
Adding back the :build task as :publish, ignoring gems for the moment. gems may eventually be archived again, but right now that's not needed for basic integration. |
||
| #27 | 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. |
||
| #26 | 13480 | tjuricek |
Creating several Rake tasks for our "hsm" configuration that are based on a Ruby API config file. The config file points to machines and services in the system which then takes care of setting up the docker-machine environment and docker-compose configuration. |
||
| #25 | 13477 | tjuricek |
More docker-compose configuration for projects in research for HSM. Added a geminabox host for the cluster, which allows for quick rebuilds. Each cluster will cache the gems it needs, and publish as well. We may want to put the overwrite commands for all publish steps by default. Note: referencing "external links" can only be done 'at runtime', so "bundle install" really needs to be run in the context of 'docker-compose up' not 'docker-compose build'. This was edited in all configured libraries so far. Finally, added the p4_project_services projects to configuration, which is running under it's own puma instance. The postgres instance is a little tricky to figure out the exact workflow. Right now I'm using the host rake db:migrate task and calling createdb manually, since we need to pass the password along. |
||
| #24 | 13474 | tjuricek | Corrected regressions that broke the API and Project services specs. | ||
| #23 | 13473 | tjuricek |
Change the name of our ':pg' rake tasks to just ':db' for some consistency. Fixed a few initial schemas to normalize on using integers for primary keys. I may need to come up with some constraints for project IDs, we'll see. |
||
| #22 | 13472 | tjuricek |
Implementation of the phoenix services side of notification handling. This is just implementation and work-in-progress. Phoenix projects will now have paths cached in the phoenix services process, which we'll use to "guess" what file changes affect which Phoenix project. We basically see a changed path, then see that it might be relevant to one of the Phoenix project stream views, and then issue a "p4 changes -m1 //stream..." to see what the last change number is. If the change number goes up, we trigger an update. Note that how this all gets configured is with an account from notification services to phoenix services, which ideally is some kind of system account that sees all relevant files. Otherwise, you'll likely get changes filtered by protections, and thus, updates may not get sent out. |
||
| #21 | 13470 | tjuricek |
Phoenix notification services, client API, including new phoenix_updater This is an interim commit containing a first pass implementation of the phoenix_updater. Notably missing parts: - The Qt API doesn't yet actually interact with the phoenix_updater - The phoenix_services web service doesn't filter out notifications I *may* end up creating another web application *just* to filter out notifications, since this may end up taking up a lot of background workers. |
||
| #20 | 13469 | tjuricek |
Initial implementation of change-commit notification services. Set up a new database just for storing webhook configuration for the notification services. It uses the stable version of Resque, which needs to be evaluated in more detail. This should be easier for an admin to monitor than something like Sidekiq, but performance evaluation needs to happen before production release. No automated tests yet, that will rely upon a Phoenix notification mechanism existing first. |
||
| #19 | 13468 | tjuricek | Set up resque worker that will trigger web hooks in the background. | ||
| #18 | 13467 | tjuricek | Add a basic notification_services endpoint that can setup a trigger entry and accept basic POST requests. | ||
| #17 | 13463 | tjuricek | Replace crappy indexing mechanism with Postgres queries. | ||
| #16 | 13462 | tjuricek |
Created a preliminary caching schema and basic database models for the p4 project services. This may break some tests momentarily until I implement caching. |
||
| #15 | 13458 | tjuricek |
Revising P4 Web API docbook documentation to become the Perforce Web Services guide. Right now this is just focused on the Qt SDK. The remaining protocol documentation, etc, will happen eventually. |
||
| #14 | 13443 | tjuricek |
Reorganized the Qt libraries into a separate part of the tree, to make it easier for CMake configuration. Added 'qt_build' and 'qt_test' tasks to at least execute tests and fail the build if they don't pass. Started the implementation of the project library interaction. Change: 1018651 Date: 3/4/15 11:43 AM Client: tjuricek_dhcp-141-n100_5959 User: tjuricek Status: pending Type: public Description: Reorganized the Qt libraries into a separate part of the tree, to make it easier for CMake configuration. Added 'qt_build' and 'qt_test' tasks to at least execute tests and fail the build if they don't pass. Started the implementation of the project library interaction. JobStatus: Jobs: Files: //web-services/p4ws-main/Rakefile //web-services/p4ws-main/p4_phoenix_services/clients/qt/p4_phoenix_services_client/CMakeLists.txt //web-services/p4ws-main/p4_phoenix_services/clients/qt/p4_phoenix_services_client/PhoenixIntegrationTests.cpp //web-services/p4ws-main/p4_phoenix_services/clients/qt/p4_phoenix_services_client/README //web-services/p4ws-main/p4_phoenix_services/clients/qt/p4_phoenix_services_client/phoenix.h //web-services/p4ws-main/p4_phoenix_services/clients/qt/p4_phoenix_services_client/phoenix/PhoenixProject.cpp //web-services/p4ws-main/p4_phoenix_services/clients/qt/p4_phoenix_services_client/phoenix/PhoenixProject.h //web-services/p4ws-main/p4_phoenix_services/clients/qt/p4_phoenix_services_client/phoenix/PhoenixServicesClient.cpp //web-services/p4ws-main/p4_phoenix_services/clients/qt/p4_phoenix_services_client/phoenix/PhoenixServicesClient.h //web-services/p4ws-main/p4_phoenix_services/clients/qt/p4_phoenix_services_client/phoenix/RequestError.cpp //web-services/p4ws-main/p4_phoenix_services/clients/qt/p4_phoenix_services_client/phoenix/RequestError.h //web-services/p4ws-main/p4_phoenix_services/clients/qt/p4_phoenix_services_client/phoenix/Session.cpp //web-services/p4ws-main/p4_phoenix_services/clients/qt/p4_phoenix_services_client/phoenix/Session.h //web-services/p4ws-main/p4_phoenix_services/clients/qt/p4_phoenix_services_client/test/PhoenixServicesClientTests.cpp //web-services/p4ws-main/p4_phoenix_services/clients/qt/p4_phoenix_services_client/test/PhoenixServicesClientTests.h //web-services/p4ws-main/p4_phoenix_services/clients/qt/p4_phoenix_services_client/test/SessionTests.cpp //web-services/p4ws-main/p4_phoenix_services/clients/qt/p4_phoenix_services_client/test/SessionTests.h //web-services/p4ws-main/p4_project_services/clients/qt/p4_project_services_client/CMakeLists.txt //web-services/p4ws-main/p4_project_services/clients/qt/p4_project_services_client/p4_project_services.h //web-services/p4ws-main/p4_project_services/clients/qt/p4_project_services_client/p4_project_services/Branch.cpp //web-services/p4ws-main/p4_project_services/clients/qt/p4_project_services_client/p4_project_services/Branch.h //web-services/p4ws-main/p4_project_services/clients/qt/p4_project_services_client/p4_project_services/Project.cpp //web-services/p4ws-main/p4_project_services/clients/qt/p4_project_services_client/p4_project_services/Project.h //web-services/p4ws-main/p4_project_services/clients/qt/p4_project_services_client/p4_project_services/View.cpp //web-services/p4ws-main/p4_project_services/clients/qt/p4_project_services_client/p4_project_services/View.h //web-services/p4ws-main/qt/CMakeLists.txt //web-services/p4ws-main/qt/p4_phoenix_services_client/CMakeLists.txt //web-services/p4ws-main/qt/p4_phoenix_services_client/PhoenixIntegrationTests.cpp //web-services/p4ws-main/qt/p4_phoenix_services_client/README //web-services/p4ws-main/qt/p4_phoenix_services_client/phoenix.h //web-services/p4ws-main/qt/p4_phoenix_services_client/phoenix/PhoenixProject.cpp //web-services/p4ws-main/qt/p4_phoenix_services_client/phoenix/PhoenixProject.h //web-services/p4ws-main/qt/p4_phoenix_services_client/phoenix/PhoenixServicesClient.cpp //web-services/p4ws-main/qt/p4_phoenix_services_client/phoenix/PhoenixServicesClient.h //web-services/p4ws-main/qt/p4_phoenix_services_client/phoenix/RequestError.cpp //web-services/p4ws-main/qt/p4_phoenix_services_client/phoenix/RequestError.h //web-services/p4ws-main/qt/p4_phoenix_services_client/phoenix/Session.cpp //web-services/p4ws-main/qt/p4_phoenix_services_client/phoenix/Session.h //web-services/p4ws-main/qt/p4_phoenix_services_client/test/PhoenixServicesClientTests.cpp //web-services/p4ws-main/qt/p4_phoenix_services_client/test/PhoenixServicesClientTests.h //web-services/p4ws-main/qt/p4_phoenix_services_client/test/SessionTests.cpp //web-services/p4ws-main/qt/p4_phoenix_services_client/test/SessionTests.h //web-services/p4ws-main/qt/p4_project_services_client/CMakeLists.txt //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeCache.txt //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/2.8.12/CMakeCCompiler.cmake //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/2.8.12/CMakeCXXCompiler.cmake //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/2.8.12/CMakeDetermineCompilerABI_C.bin //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/2.8.12/CMakeDetermineCompilerABI_CXX.bin //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/2.8.12/CMakeSystem.cmake //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/2.8.12/CompilerIdC/CMakeCCompilerId.c //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/2.8.12/CompilerIdC/a.out //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/2.8.12/CompilerIdCXX/CMakeCXXCompilerId.cpp //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/2.8.12/CompilerIdCXX/a.out //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/CMakeDirectoryInformation.cmake //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/CMakeOutput.log //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/Makefile.cmake //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/Makefile2 //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/TargetDirectories.txt //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/cmake.check_cache //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/p4_project_services_client.dir/DependInfo.cmake //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/p4_project_services_client.dir/build.make //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/p4_project_services_client.dir/cmake_clean.cmake //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/p4_project_services_client.dir/cmake_clean_target.cmake //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/p4_project_services_client.dir/depend.make //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/p4_project_services_client.dir/flags.make //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/p4_project_services_client.dir/link.txt //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/p4_project_services_client.dir/progress.make //web-services/p4ws-main/qt/p4_project_services_client/build/CMakeFiles/progress.marks //web-services/p4ws-main/qt/p4_project_services_client/build/Makefile //web-services/p4ws-main/qt/p4_project_services_client/build/cmake_install.cmake //web-services/p4ws-main/qt/p4_project_services_client/p4_project_services.h //web-services/p4ws-main/qt/p4_project_services_client/p4_project_services/Branch.cpp //web-services/p4ws-main/qt/p4_project_services_client/p4_project_services/Branch.h //web-services/p4ws-main/qt/p4_project_services_client/p4_project_services/Project.cpp //web-services/p4ws-main/qt/p4_project_services_client/p4_project_services/Project.h //web-services/p4ws-main/qt/p4_project_services_client/p4_project_services/View.cpp //web-services/p4ws-main/qt/p4_project_services_client/p4_project_services/View.h |
||
| #13 | 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. |
||
| #12 | 13433 | tjuricek |
Restructure 'builds' to be blessed versions of things to be used by clients. The gems/ folder contains all the ruby distributables. Eventually, these will likely be published to Rubygems. The other folders are source projects that can be included into dependent streams. These are 'versioned' against the last build that we ideally run some integration tests against. |
||
| #11 | 13431 | tjuricek | Try out chmod before updating the build. | ||
| #10 | 13429 | tjuricek | See if I can read directly from the source file. | ||
| #9 | 13428 | tjuricek |
Add steps to create 'build/' output directory for automated builds. This does require a 'p4' command line client in order to grab the latest changelist number, which may/may not be easily setup. |
||
| #8 | 13427 | tjuricek | Put retry logic for service start that depends upon curl. | ||
| #7 | 13426 | tjuricek | Added top level rake build task for automated builds. | ||
| #6 | 13420 | tjuricek |
Setup the main directory to launch specs in subprojects and a unicorn-based daemon via rake. See rake -T for details, but this should allow for CI builds to collect output. |
||
| #5 | 13419 | tjuricek | The p4_project_services specs now run that provide basic create-read ability. | ||
| #4 | 13418 | tjuricek | Added p4_project_services to development config.ru, and reconfigured p4 web api client tests to use the new paths. | ||
| #3 | 13417 | tjuricek |
Added a 'rake work/config.ru' task, that creates a local rack configuration. This now includes the project services, which is not yet mounted. The p4 web api tests still pass though. |
||
| #2 | 13416 | tjuricek |
Set up the p4_web_api related projects to be loaded by the parent Gemfile to make it a little easier to launch a test p4d with different seed data. Also fixed a couple of minor issues related to the client api. You'll notice that the 'rake api_reset api_init' task sets up a p4d for the p4_web_api tests, where the 'rake proj_reset proj_init' tasks set up p4d for project services testing. An example p4_web_api.ru that can be used for launching just the p4_web_api: require 'p4_web_api' # Do *not* let your development environment variables pollute how the p4 web api runs! ENV.keys.select { |k| k =~ /^P4/ }.each { |k| ENV.delete(k) } api = P4WebAPI::App.new puts 'changing paths' api.settings.token_path = '/Users/tjuricek/dev/p4ws/work/tokens' api.settings.workspace_folder = '/Users/tjuricek/dev/p4ws/work/workspaces' api.settings.p4 = {'port' => 'localhost:1666', 'charset' => 'auto'} run api |
||
| #1 | 13415 | tjuricek | Add some basic utility methods to the top level. | ||