1450094 - rerunTask should take an optional `force` arg, and refuse to rerun completed tasks without it

Status: RESOLVED WORKSFORME

(Taskcluster :: Services, enhancement)

Description

[Aki Sasaki (not active)]

In bug 1450012, one of the things we're discussing is the fallout from multiple people rerunning the same release task. The scenario is:

- I noticed task X failed using queue polling; I reran task X
- task X completed successfully; the graph continued running.
- RyanVM noticed task X had failed via treeherder. Treeherder keeps the failed task symbol visible, even if the task in question has been acted upon.
- RyanVM reran task X
- RyanVM noticed that I had reran task X, and cancelled task X.

This is the problem: now task X's latest artifacts are empty except for logs, and downstream tasks will fail. This is especially problematic for release graphs, where everything is cot verified.

We're discussing various ways to avoid these problems. One is disabling `taskcluster task rerun` if the task has completed successfully, unless we pass a `--force` arg.

Is this doable? What time frame would we be looking at if it were?

Comment 1

[Aki Sasaki (not active)]

We now have a rerun action in bug 1450012.