/* A summary of depots in the system, with information provided by the `p4 depots` command. */ function DepotsCommand(data) { Object.defineProperties(this, { /* The depot name. */ "depot": { value: data ? data.depot : undefined, enumerable: true, writable: true }, /* If the Type: is local, spec, or archive, set the map to point to the relative location of the depot subdirectory. The map must contain the `...` wildcard; for example, a local depot new might have a Map: of `new/...`. If the Type: is remote, set the map to point to a location in the remote depot's physical namespace, for example, `//depot/new/rel2/...`. This directory will be the root of the local representation of the remote depot. */ "map": { value: data ? data.map : undefined, enumerable: true, writable: true }, /* `local`, `remote`, `spec`, `stream`, `unload`, `archive` or `tangent`. A local depot is writable, and is the default depot type. Files reside in the server's root directory and are managed directly by the server. A stream depot is also writable, but contains streams, a type of branch that includes hierarchy and policy. A remote depot references files that reside on other servers, and cannot be written to. The spec depot, if present, automatically archives edited forms. The unload depot, if present, holds infrequently-used metadata (about old client workspaces and labels) that has been unloaded with the p4 unload command. An archive depot is used in conjunction with the p4 archive and p4 restore commands to facilitate offline (or near-line) storage of infrequently-accessed revisions, typically large binaries. A tangent depot defines a read-only location that holds tangents created by the p4 fetch -t command. The tangent depot named tangent is automatically created by p4 fetch -t if one does not already exist. */ "type": { value: data ? data.type : undefined, enumerable: true, writable: true }, /* For stream depots, the optional depth to be used for stream paths in the depot, where depth specifies the number of slashes following the depot name of a stream. ] This field is used when streams are being created. The default is 1, matching the traditional stream name. You cannot update this value once streams or archive data exist in a depot. */ "streamDepth": { value: data ? data.streamDepth : undefined, enumerable: true, writable: true }, /* A short description of the depot’s purpose. Optional. */ "description": { value: data ? data.description : undefined, enumerable: true, writable: true } }); } module.exports = DepotsCommand;
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 19553 | swellard | Move and rename clients | ||
//guest/perforce_software/helix-web-services/main/source/clients/2016.1.0/javascript/lib/models/depots_command.js | |||||
#2 | 19169 | tjuricek | JavaScript Client SDK jobs CRUD test, with supprt for "additionalProperties" in the swagger definition. | ||
#1 | 19053 | tjuricek |
Rebuild JavaScript Client SDK. The JavaScript client now is a "typed" approach that tends 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. |