Confirmed users
142
edits
ReleaseEngineering/How To/Self Provision a TaskCluster Windows Instance: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/How To/Self Provision a TaskCluster Windows Instance (view source)
Revision as of 10:21, 24 April 2018
, 24 April 2018Added information about rerunning task steps
m (Added link to bug 1368961 for integration with one-click-loaner workflow) |
(Added information about rerunning task steps) |
||
| Line 35: | Line 35: | ||
7) Connect with screen resolution 1280x1024 ! Note, it is '''important''' to use this resolution for gecko tests, since this is the screen size used by the tests, and the screen size cannot change once you have made a connection. | 7) Connect with screen resolution 1280x1024 ! Note, it is '''important''' to use this resolution for gecko tests, since this is the screen size used by the tests, and the screen size cannot change once you have made a connection. | ||
== Rerunning tasks after they have completed == | |||
If you want to rerun a step after the task has completed, there is a script for each command in the task payload. They are named like this: | |||
Z:\task_XXXXXXX\command_000000_wrapper.bat | |||
Z:\task_XXXXXXX\command_000001_wrapper.bat | |||
Z:\task_XXXXXXX\command_000002_wrapper.bat | |||
.... | |||
Simply run them by hand to reproduce any of the task steps. If you wish to make changes, feel free to edit them. After the loan expires, the task directory, including all your changes, will be deleted. Therefore make sure to keep track of any changes that need to be put back in the gecko build system. | |||
= For earlier versions of generic-worker (<10.5.0) = | = For earlier versions of generic-worker (<10.5.0) = | ||