Pipelines
Last updated
Last updated
Delete pipelines from an aggregator.
Deleted
Pipelines from an aggregator.
OK
DNS label format as of defined on RFC1123
Kind of deployment used when deploying this pipeline
Pipeline configuration history entry.
Pipeline status history entry.
Resource profile model.
total number of checks associated with the pipeline.
total number of checks with ok status.
total number of checks with running status.
Create pipeline within an aggregator. The pipeline name must be unique within the aggregator. The resource profile must exist already. If you don't provide one, it will default to "best-effort-low-resource". Use them to easily deploy configured agents to the aggregator.
DNS label format as of defined on RFC1123
Kind of deployment used when deploying this pipeline
If true, this will automatically create a set of Pipeline checks to validate that the configured output services are reachable.
If set to true:
If all checks associated with the pipeline run successfully, the status of the pipeline will be switched to CHECKS_OK and the deployment will be executed.
If any of the checks associated with the pipeline fails, the status of the pipeline will be switched to CHECKS_FAILED and the deployment of the pipeline will be blocked.
If set to false (default):
If all checks associated with the pipeline run successfully, the status of the pipeline will be switched to CHECKS_OK and the deployment will be executed.
If any of the checks associated with the pipeline fails, the status of the pipeline will be switched to CHECKS_FAILED and the deployment of the pipeline will be executed.
Created
Kind of deployment used when deploying this pipeline
Pipeline configuration history entry.
Pipeline status history entry.
Resource profile model.