/* Defines the triggers table, like it would appear in the output to the `p4 triggers` command. */ function Triggers(data) { Object.defineProperties(this, { /* A list of trigger definitions. A trigger definition contains four fields that specify the name of the trigger, the type of event that should trigger the execution of the script, the paths that should be affected by the trigger, the location of the script, and other trigger type-dependent information. When the condition specified in a trigger definition is satisfied, the associated script or program is executed. Example: `trig1 change-submit //depot/dir/... "/usr/bin/s1.pl %changelist%"` See the Helix Versioning Engine Administrator Guide for more details on trigger definitions. */ "triggers": { value: data ? data.triggers : undefined, enumerable: true, writable: true } }); } module.exports = Triggers;
# | 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/triggers.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. |