This group describes attributes specific to pipelines within a Continuous Integration and Continuous Deployment (CI/CD) system. A pipeline in this case is a series of steps that are performed in order to deliver a new version of software. This aligns with the Britannica definition of a pipeline where a pipeline is the system for developing and producing something. In the context of CI/CD, a pipeline produces or delivers software.
Attribute | Type | Description | Examples | Stability |
---|---|---|---|---|
cicd.pipeline.name | string | The human readable name of the pipeline within a CI/CD system. | Build and Test ; Lint ; Deploy Go Project ; deploy_to_environment | |
cicd.pipeline.run.id | string | The unique identifier of a pipeline run within a CI/CD system. | 120912 | |
cicd.pipeline.task.name | string | The human readable name of a task within a pipeline. Task here most closely aligns with a computing process in a pipeline. Other terms for tasks include commands, steps, and procedures. | Run GoLang Linter ; Go Build ; go-test ; deploy_binary | |
cicd.pipeline.task.run.id | string | The unique identifier of a task run within a pipeline. | 12097 | |
cicd.pipeline.task.run.url.full | string | The URL of the pipeline run providing the complete address in order to locate and identify the pipeline run. | https://github.com/open-telemetry/semantic-conventions/actions/runs/9753949763/job/26920038674?pr=1075 | |
cicd.pipeline.task.type | string | The type of the task within a pipeline. | build ; test ; deploy |
cicd.pipeline.task.type
has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
Value | Description | Stability |
---|---|---|
build | build | |
deploy | deploy | |
test | test |
Was this page helpful?
Thank you. Your feedback is appreciated!
Please let us know how we can improve this page. Your feedback is appreciated!