Back to index
Summary
Run the specified trigger, returns the flowRuntimeId.The following parameters are valid combinations for each trigger type:
-
Application: [
projectName
,applicationName
,triggerName
] -
Catalog item: [
projectName
,catalogName
,catalogItemName
,triggerName
] -
Pipeline: [
projectName
,pipelineName
,triggerName
] -
Release: [
projectName
,releaseName
,triggerName
] -
Procedure: [
projectName
,procedureName
,triggerName]
applicationNameStringoptionalThe name of the application. parsedWebhookDataStringoptionalJSON with parsed webhook data to be set on a pipeline/release/procedure run. pathStringoptionalProperty path string. pipelineNameStringoptionalThe name of the pipeline. procedureNameStringoptionalName for the procedure; must be unique within the project. projectNameStringoptionalThe name for the project that must be unique among all projects. releaseNameStringoptionalThe name of the release. scmSyncNameStringoptionalThe name of the scm sync. triggerNameStringoptionalThe name of the trigger. webhookDataStringoptionalThe webhook data to be set on the pipeline/release/procedure run. webhookHeadersStringoptionalThe webhook headers in JSON format to be set on the pipeline/release/procedure run. |
Usage
Perl
$cmdr->runTrigger( # optionals );
ectool
ectool runTrigger \ # optionals
Examples
Perl
# for pipeline $cmdr->runTrigger( {projectName => "qe proj", pipelineName => "qe pipeline name", triggerName => "qe trigger 1", webhookData => "test", webhookHeaders => "Test", parsedWebhookData => "\"{\"branch\": \"master\"}\""}); # for procedure $cmdr->runTrigger( {projectName => "qe proj", procedureName => "qe procedure name", triggerName => "qe trigger 1", webhookData => "test", webhookHeaders => "Test", parsedWebhookData => "\"{\"branch\": \"master\"}\""});