- 필수 기능
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- 디지털 경험
- 소프트웨어 제공
- 보안
- 로그 관리
- 관리
- 인프라스트럭처
- ci
- containers
- csm
- ndm
- otel_guides
- overview
- slos
- synthetics
- tests
- 워크플로
You can send custom pipelines through HTTP using the public API endpoint. For more information about how pipeline executions are modeled, see Pipeline Data Model and Execution Types.
Pipeline Visibility | Platform | Definition |
---|---|---|
Custom tags and measures at runtime | Custom tags and measures at runtime | Configure custom tags and measures at runtime. |
Manual steps | Manual steps | View manually triggered pipelines. |
Parameters | Parameters | Set custom parameters when a pipeline is triggered. |
Partial retries | Partial pipelines | View partially retried pipeline executions. |
Pipeline failure reasons | Pipeline failure reasons | Identify pipeline failure reasons from error messages. |
Queue time | Queue time | View the amount of time pipeline jobs sit in the queue before processing. |
The CI Pipeline List and Executions pages populate with data after the pipelines are accepted for processing.
The CI Pipeline List page shows data for only the default branch of each repository.
Additional helpful documentation, links, and articles: