Make job expiration time relatable
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem
In order to prevent missing dependency error states/scenarios from even happening in the first place, it would be wishful to make it possible to have artifact expiration time be related to pipeline duration (clock begins ticking when pipeline finishes).
Usecase
Artifact expiration is currently set from artifact creation time, however, there are other jobs within the same pipeline or even downstream pipelines that depend on those. More granularity towards setting expiration might help here to remove unnecessary failing due to artifacts being removed to fast.
The current workaround consists of making the expiration time longer than necessary.
Further information
Follow up from #6144 (closed)