- id: localhost
- name: Local P4D
- description: Local P4D used for testing
- P4PORT: localhost:1666
- P4CHARSET: utf8
| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #1 | 19803 | tjuricek | Setting up the server to be deployable as a servlet, and adding custom "prefix" addition t...o all routes. It's not completely clear exactly when you'd want to do this, but, you could include the hws.jar in your app server and run this way. This adds a new "servlet example project" that we use to execute a basic test in the new suite. « |
9 years ago | |
| //guest/perforce_software/helix-web-services/main/source/server/config/p4ds/localhost | |||||
| #4 | 19625 | tjuricek | Report a 500 for misconfigured P4CHARSET settings, make sure status reports an error, and... make the log entry meaningful. « | 9 years ago | |
| #3 | 19281 | tjuricek | Adding non-unicode version of the default 16.1 p4d run. | 9 years ago | |
| #2 | 19277 | tjuricek | Add self-signed SSL configuration variation (just with the 16.1 p4d) for testing. No bu...gs were actually uncovered, though it may be useful to debug environments. (If people don't have a properly patched JVM with the JCE extensions, this test will fail.) « |
9 years ago | |
| #1 | 19053 | tjuricek | Rebuild JavaScript Client SDK. The JavaScript client now is a "typed" approach that ten...ds to be similar in approach to the other clients, based on the swagger definition for the platform version. Importantly, client SDK tests are individual scripts (that run under node) that are actually controlled via TestNG. This approach now lets us use a consistent test reporting format so we can at least collect reports from each of the jobs. The documentation is still in progress, that I want to validate as the tests are generated. « |
9 years ago | |