canmove, Confirmed users
1,394
edits
ReleaseEngineering/Buildslave Startup Process: Difference between revisions
ReleaseEngineering/Buildslave Startup Process (view source)
Revision as of 23:31, 19 April 2011
, 19 April 2011→Windows XP
m (→Windows XP: Trac, you rot my brain.) |
|||
| Line 34: | Line 34: | ||
== Test == | == Test == | ||
=== Windows XP === | === Windows XP === | ||
startTalos.bat is in the Startup Items subfolder of the Programs folder, so at login by cltbld (which happens automatically), this batch file runs. It skips tac file generation for refimages, or if the tac file or a control file (c:\buildbot-tac.control) already exists. Otherwise it invokes c:\tools\buildbot-helpers\buildbot-tac.py to generate the tac file. Once that is done, it sets the screen size (using dc.exe), stops and starts Apache, empties the twistd.log, waits 60 seconds, and starts the slave. There's no loop here, as there is for build slaves. | startTalos.bat is in the Startup Items subfolder of the Programs folder, so at login by cltbld (which happens automatically), this batch file runs. Note that it contains passwords, so it is not in opsi-packages, and apparently not on the OPSI server at all, meaning it ships with the refimage. It skips tac file generation for refimages, or if the tac file or a control file (c:\buildbot-tac.control) already exists. Otherwise it invokes c:\tools\buildbot-helpers\buildbot-tac.py to generate the tac file. Once that is done, it sets the screen size (using dc.exe), stops and starts Apache, empties the twistd.log, waits 60 seconds, and starts the slave. There's no loop here, as there is for build slaves. | ||
=== Windows 7 === | === Windows 7 === | ||
Talos Windows 7 systems are not administered by OPSI, so the various scripts are installed by hand. I don't know how they work yet | Talos Windows 7 systems are not administered by OPSI, so the various scripts are installed by hand. I don't know how they work yet | ||