This repository has been archived by the owner on Jul 2, 2024. It is now read-only.
DEVPROD-2707: Avoid modifying parent patch when restarting downstream tasks #2251
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.
DEVPROD-2707
Description
This PR fixes a bug where restarting a downstream task via the VersionRestartModal would also restart all of the tasks in the parent patch.
The issue seems to stems from a change in restart logic made in Evergreen four months ago. When restarting a downstream task from the UI, the payload looks like the following:
However, according to the function that restarts versions, an empty
taskIds
array means that ALL completed tasks belonging to the version will be restarted. See screenshot below:The given payload means that
"downstream-task"
will be correctly restarted in the child patch, but so will every other completed task in the parent patch.To correct this we can just remove any items from the payload that have an empty
taskIds
array.Testing