Conventions for ci/CD pipelines

[thompson-tomo]

Area(s)

area:new

Is your change request related to a problem? Please describe.

I want to be able to clearly capture all my traces in one central location which includes test

Describe the solution you'd like

Semantic conventions are defined which covers attributes which would be populated by the ci/CD system

• cicd.provider who is running the ci/CD ie github
• cicd.pipelineid a unique identifier for this build pipeline instance
• cicd.pipelinebame a user definable name for this build pipeline
• cicd.pipelineurl a permalink to view this build pipeline instance
• cicd.stagename a user definable name for this stage of the build pipeline
• cicd.stepid a unique identifier for the step
• cicd.stepname a user definable name for this step of the build stagr
• cicd.stepurl a permalink to view this step
• cicd.result strongly type field of success/failure
• cicd.trigger what resulted in the running of the pipeline.

Describe alternatives you've considered

No response

Additional context

No response

[arminru]

Hey @thompson-tomo!
This work is already in progress. Please see https://github.com/open-telemetry/community/blob/main/projects/ci-cd.md for details on the ongoing project, https://github.com/open-telemetry/community#specification-sigs for the group's meeting schedule, and #1075 for their first proposal. You're welcome to join and contribute to the effort 🙂