124
edits
ReleaseEngineering/How To/Self Provision a TaskCluster Windows Instance: Difference between revisions
ReleaseEngineering/How To/Self Provision a TaskCluster Windows Instance (view source)
Revision as of 15:07, 16 July 2018
, 16 July 2018→For generic-worker 10.5.0 onwards
(Added information about handling a task exception for an interactive task.) |
|||
| Line 45: | Line 45: | ||
- Administrators | - Administrators | ||
6) Make sure that if your payload mounts any artifacts, that the task ID(s) are included as a list in top level property <code>dependencies</code> ('''not''' under <code>payload</code>) | 6) Make sure that if your payload mounts any artifacts, that the task ID(s) are included as a list in top level property <code>dependencies</code> ('''not''' under <code>payload</code>) | ||
So if it says | |||
mounts: | |||
- directory: . | |||
content: | |||
taskId: HUqhbXTMTXSXYEM6K2H3wA | |||
Add (at the top level indent) | |||
dependencies: | |||
- HUqhbXTMTXSXYEM6K2H3wA | |||
7) Submit the task. If the task resolves as exception and doesn't run, '''check the task log file'''. It should provide more information about the cause.<br /> | 7) Submit the task. If the task resolves as exception and doesn't run, '''check the task log file'''. It should provide more information about the cause.<br /> | ||
8) When the task successfully starts, go to ''Run Artifacts'' to see the <code>rdpInfo.txt</code> file appear with rdp connection information.<br /> | 8) When the task successfully starts, go to ''Run Artifacts'' to see the <code>rdpInfo.txt</code> file appear with rdp connection information.<br /> | ||