Order jobs in pipeline tracing to ensure job links are created in order
What does this MR do and why?
When creating span links for pipeline tracing, the ProcessJobs
class assumes the jobs are in the order of execution.
This can result in re-run jobs having the span link in the wrong direction as the API can return the most recent job first.
Modify the jobs processing spec to check out-of-order job links are created correctly.
Closes gitlab-org/opstrace/opstrace#2075 (closed)
Author Check-list
-
Has documentation been updated?
Edited by Joe Shaw