We’re running scheduled pipelines every 30 minutes to check if any relevant component / dependency got updated and if so, this triggers the build/test/deploy pipeline of the project.
This results in the problem that we may have several pages of successful pipeline logs, as the “Check for update” succeeded but we have trouble finding the last one that actually found an updated component and then triggered another pipeline.
It would be nice to declare a pipeline (log) as outdated so that it gets removed from the list of succeeded pipelines. Or, if pipelines could be tagged or labelled, filtering could be another strategy to selectively list pipeline logs.
Is any of that possible somehow?