Confirmed users
656
edits
Sheriffing/Manifest Scheduling: Difference between revisions
Jump to navigation
Jump to search
→Add New Jobs
| Line 55: | Line 55: | ||
There is currently no way to specify test manifests when adding new jobs via Treeherder's "Add New Jobs" UI. This means that it can't be used to fill in tasks for the purpose of bisecting a regression. There are plans to add this feature in the future. If used, "Add New Jobs" would simply run the same manifests that ran | There is currently no way to specify test manifests when adding new jobs via Treeherder's "Add New Jobs" UI. This means that it can't be used to fill in tasks for the purpose of bisecting a regression. There are plans to add this feature in the future. If used, "Add New Jobs" would simply run the same manifests that ran | ||
One risk here is that it will be more difficult (but still possible) to schedule a mozilla-central only task on autoland for the purposes of bisecting a regression caught on central. You'll now need to make sure that you use "Add New Jobs" | One risk here is that it will be more difficult (but still possible) to schedule a mozilla-central only task on autoland for the purposes of bisecting a regression caught on central. You'll now need to make sure that you use "Add New Jobs" ''on a backstop push'' as that will run all test manifests. Then you can bisect the task like normal. | ||
In the future we plan to get rid of all mozilla-central only tasks and run them on an interval on autoland instead. | In the future we plan to get rid of all mozilla-central only tasks and run them on an interval on autoland instead. | ||