Consider findWorstWarningBetween for branches of running builds #806
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #794.
Use
StatusAndTiming#findWorstWarningBetweento inform the status of branches while a build is still running.Detection of
WarningActions in enclosed nodes is the most reliable way to determine a status forstageorparallelbranches. PreviouslyStatusAndTiming#findWorstWarningBetweenwas only considered for completed pipelines.Testing done
TODO:I will need to implement a test utility to gather the status of stages and parallel branches for a running pipeline. Currently this is only supported inStagesAndParallelBranchesVisitorfor completed pipelines.Submitter checklist