Closed Bug 1402884 Opened 7 years ago Closed 4 years ago

[checks] Cancel jobs that are obsolete because of new commits

Categories

(Taskcluster :: Services, enhancement, P5)

Product:
Taskcluster
Component:
Services
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: kats, Unassigned)

References

Details

If you have the taskcluster-github integration set up on a github repo, and submit a PR, the integration tool will run the necessary jobs as specified in the .taskcluster.yml file. However, if, while those jobs are running, you update the commits in the PR, taskcluster will not cancel the now-obsolete jobs that were already started. It will just start a new set of jobs for the updated PR commits. It would be nice if taskcluster cancelled the old jobs so that they don't waste machine time.
Priority: -- → P5
Severity: normal → enhancement
Another user complained about this, I believe, not long ago before Christmas. The ability to cancel things may come with Checks
Severity: enhancement → normal
Component: Github → Services
Blocks: checks
Summary: Cancel jobs that are obsolete because of new commits → [checks] Cancel jobs that are obsolete because of new commits

This is good background for a rethink of the GitHub integration.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.