canmove, Confirmed users
1,394
edits
ReleaseEngineering/Buildslave Startup Process: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/Buildslave Startup Process (view source)
Revision as of 22:54, 19 April 2011
, 19 April 2011→Build
(→Build) |
|||
| Line 25: | Line 25: | ||
buildbot.bat is in cltbld's "Startup Items". It is installed via OPSI, but | buildbot.bat is in cltbld's "Startup Items". It is installed via OPSI, but | ||
it's not in the OPSI hg repo, because it contains passwords. buildbot.bat runs | it's not in the OPSI hg repo, because it contains passwords. buildbot.bat runs | ||
buildbot-tac.py, via a checkout of http://hg.mozilla.org/build/tools at | |||
d:\tools. That checkout is only done once | d:\tools. That checkout is only done once (in the refimage, I think) | ||
Once buildbot-tac.py has created the tac file, buildbot.bat runs | Once buildbot-tac.py has created the tac file, buildbot.bat runs start-buildbot.bat, which sets up some VC++ variables (using guess-msvc.bat, which is part of MozillaBuild) and runs start-buildbot.sh, which finally runs 'buildbot start' in the appropriate directory. | ||
start-buildbot.bat, which sets up some VC++ variables and runs | |||
start-buildbot.sh, which finally runs 'buildbot start' in the appropriate | Both start-buildbot.bat and start-buildbot.sh have loops in them to try to start buildbot multiple times. These were introduced in {{bug|550815}} because (by my read) a race condition with some OPSI startup stuff was occasionally killing the buildslave during the startup process. | ||
== Test == | == Test == | ||
Talos windows systems are not administered by OPSI, so the various scripts are installed by hand. I don't know how they work yet | Talos windows systems are not administered by OPSI, so the various scripts are installed by hand. I don't know how they work yet | ||