Execute Published Pipeline
Triggers the asynchronous execution of a named, published pipeline within the specified project.
The pipeline must be published to the target environment before it can be executed. On success, returns a pipelineExecutionId that can be used to track or query the execution status.
Key behaviours:
- By default, the latest published version of the pipeline is executed. Use
versionNameto target a specific artifact version. - If no
agentIdis provided, the default agent configured for the target environment is used. - Use
executionTagto control concurrency — only one execution per tag is permitted to run at a time within a given environment. A409 Conflictis returned if an execution with the same tag is already in progress. - Runtime variable values can be overridden per-execution using
scalarVariables(key-value pairs) orgridVariables(two-dimensional string arrays), without modifying the published pipeline definition. - A
410 Goneis returned if the pipeline has been disabled.
Authorizations
a valid bearer token
Path Parameters
Body
Environment pipeline is published to
255"Dev Env"
Name of the pipeline to execute
1"My pipeline"
Optional agentId to execute the pipeline. If not specified the default agent for the provided environment will be used
"3fa85f64-5717-4562-b3fc-2c963f66afa6"
Optional execution tag, this allows control of pipeline execution concurrency. Only 1 pipeline execution is allowed to run per execution tag in a given environment.
"tag1"
Optional map of grid variable names to two-dimensional string arrays, used to override grid variable values for this execution without modifying the published pipeline definition
Optional map of scalar variable names to their override values for this execution, without modifying the published pipeline definition
Optional artifact version name of the pipeline to execute. If not specified the latest version will be executed
"1.1.0"
Response
Pipeline executed
Identifier of executing pipeline
"1398aa31-af57-4a6a-9752-27c2e8556c3f"
