ReleaseEngineering/TryServer: Difference between revisions

m
(Add section about re-running tasks with custom parameters)
Line 130: Line 130:
== Re-running tasks with custom parameters from Treeherder ==
== Re-running tasks with custom parameters from Treeherder ==


Load a job you're interested to re-run (Note it currently only work for [https://searchfox.org/mozilla-central/source/taskcluster/taskgraph/actions/retrigger_mochitest.py#30-31 some jobs]). The details panel should open up. Look for the 3 dots icon ("Other job details") and select "Custom actions...".
In treeherder, select the job you want to re-run (Note: it currently only works for [https://searchfox.org/mozilla-central/source/taskcluster/taskgraph/actions/retrigger_mochitest.py#30-31 some jobs]). The details panel should open. Look for the 3 dots icon ("Other job details") and select "Custom actions...".


[[File:Custom Taskcluster Job Actions.png|thumb|Treeherder modal to request an action associated to a task]]
[[File:Custom Taskcluster Job Actions.png|thumb|Treeherder modal to request an action associated to a task]]


The <tt>retrigger-mochitest</tt> action (TODO: A better name is needed) is the one selected in the dropdown menu. You can now modify some parameters of the task and select "Trigger". This will schedule the task with your specified parameters. The task will be labeled as <tt>custom-<original_task_name></tt>.
The <tt>retrigger-mochitest</tt> action (TODO: A better name is needed) is the one selected in the drop-down menu. Modify the task parameters as desired and select "Trigger". This will schedule the task with your specified parameters. The new task will be labeled as <tt>custom-<original_task_name></tt>.


Some of the parameters that you can change are (see screenshot above):
Some of the parameters that you can change are (see screenshot above):
Line 141: Line 141:
* Modify Python's logging level
* Modify Python's logging level
* Path of the test to execute
* Path of the test to execute
* Gecko preference (think of <tt>about:config</tt>)
* Gecko preferences (think of <tt>about:config</tt>)
* Run a test repeatedly
* Run a test repeatedly
* Run until the test fails
* Run until the test fails
Confirmed users
1,759

edits