Confirmed users
3,990
edits
CIDuty/How To/Deprecated / Archived/Slave Management: Difference between revisions
Jump to navigation
Jump to search
CIDuty/How To/Deprecated / Archived/Slave Management (view source)
Revision as of 19:18, 15 April 2014
, 15 April 2014→Windows
| Line 136: | Line 136: | ||
== Start up flow == | == Start up flow == | ||
This is how buildbot starts: | |||
scheduled task (after login) -> start talos bat -> C:\slave\runslave.py | |||
== | We started logging the start up of runslave.py under C:\slave\runslave.log | ||
We do some clean up steps inside of the .bat file. | |||
TODO: correct file names and paths | |||
=== Trigger buildbot the natural way === | |||
You're logged in and you want to trigger buildbot the same way as if the machine had come back from a reboot. | |||
Go to the Task Library, change the property of the scheduled task to allow running manually and hit "run" on the task (more or less). | |||
== Infra setup == | |||
The Windows machines are managed via GPO. | |||
The Windows test machines have the on-board graphics card and a third party graphic card: | |||
[[File:Xp_-_two_graphic_cards.png]] | |||
== Windows basics == | |||
=== Command Prompt === | === Command Prompt === | ||
Aka cmd.exe, you can start it by clicking on the "start" button and then click on "Run..." | Aka cmd.exe, you can start it by clicking on the "start" button and then click on "Run..." | ||