Notes from CICD SIG meeting:

Right now, vendor's probably have a mix/mash between wether or not their ID's are globally unique. Decoupling from vendor implementations, should this value be unique, especially when correlated with pipeline.run.* and pipeline.task.run.* attributes.

This comes up when a task or pipeline are re-run. Vendors today often include an attribute like run.attempt = some number but keep the id the same.

ie. when correlating *.run.id with *.run.{status,result} will we need an attribute that on the span/event correlates that unique run?

If we use resource entities for cicd pipeline can we identify the pipeline and pipeline run with unique task runs there-within.

The correlation of task.run.id and pipeline.run.id should be unique globally, but task.run.id is unique WITHIN the pipeline.run. Between multiple pipeline run id's, you could have the same task id within each pipeline run.

The two use cases:

want to be able to track one task between multiple runs for detecting things like flakiness. do you use the same id or different ids.
identifying id when you want to address one task run when linking to it. the url for the task run can be clearly identified there. pipeline run id in combination with task run id should be unique globally.

Bringing this over to implementation:

we need to update the description
the combination of pipeline run.id + task run.id should be unique
the task.run.id may be re-used between re-runs of the same pipeline
it may be used to correlate the same task between runs

Clarification to cicd.pipeline.task.run.id #3566

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Clarification to `cicd.pipeline.task.run.id` #3566