Introduce `UpdateJobResult` and `PatchState`
What does this MR do?
Introduce UpdateJobResult
and PatchState
Currently:
-
PatchTrace
usedUpdateState
causing some confusion on handling of the different values -
UpdateState
as a return ofUpdateJobResult
is inflexible to append the result with additional data, likecanceled
orupdate-interval
This:
- Introduces an explicit
PatchState
with a states directly supported byPatchTrace
- Make
UpdateJob
to provideUpdateJobResult
- It retains all current behavior for handling data
Why was this MR needed?
This is related to discussion about trace handling improvements for Runner: gitlab#232533 (comment 405974271).
This is needed to provide a better maintainability and explicitness of data processing.
Edited by Kamil Trzciński (Back 2025-01-01)