/* Defines a unique Git Fusion branch. */ function GitFusionRepoBranchConfig(data) { Object.defineProperties(this, { /* Alphanumeric ID for the git branch. _Do not change this value once this repo has been cloned_. */ "gitBranchId": { value: data ? data.gitBranchId : undefined, enumerable: true, writable: true }, /* Defines a name specified in a local repo for a Git branch. A valid Git branch name. Do not edit this value after you clone the repo. */ "gitBranchName": { value: data ? data.gitBranchName : undefined, enumerable: true, writable: true }, /* Defines a Perforce workspace view mapping that maps Perforce depot paths (left side) to Git work tree paths (right side). Correctly formed mapping syntax; must not include any Perforce stream or spec depots, and all depot paths on the right side must match exactly across all branch definitions. You can add and remove only certain types of Perforce branches from this view after you clone the repo. */ "view": { value: data ? data.view : undefined, enumerable: true, writable: true }, /* Defines a Perforce stream that maps to the Git branch. Provide a stream name using the syntax //streamdepot/mystream. A Git Fusion branch can be defined as a view or a stream but not both. If your branch is defined as stream, it can include only one stream. */ "stream": { value: data ? data.stream : undefined, enumerable: true, writable: true }, /* Prohibit git pushes that introduce commits to the branch. */ "readOnly": { value: data ? data.readOnly : undefined, enumerable: true, writable: true } }); } module.exports = GitFusionRepoBranchConfig;
# | 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/git_fusion_repo_branch_config.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. |