Difference between revisions of "Adding a buildslave"
m |
m |
||
| Line 1: | Line 1: | ||
To add a slave: | To add a slave: | ||
| − | + | # Install python (can't build arma without it anyway, duh) | |
| − | + | # Install twisted | |
| − | + | # Install buildbot (buildmaster is 0.75, portage has 0.74, don't know if that's a problem or not) | |
| − | + | # <code>svn co https://armagetronad.svn.sourceforge.net/svnroot/armagetronad/support/buildbot/buildslave</code> | |
| − | + | # <code>cd buildslave</code> | |
| − | + | # <code>vi buildbot.tac</code> | |
| − | + | # Change password, username, and the other thing (root directory) | |
| − | + | # <code>make start</code> | |
| − | That's to run a slave on your machine. To actually add it to the system, I need to give you a user and password and do some work on the buildmaster. Also, as noted in the buildbot.tac file, please don't commit your buildslave directory after you create your slave. It's arguable whether or not this should even be in svn since it's just the generated files with some added comments. But don't commit it after you put your user and pass in it, because then the whole world can see it. Commit it after you generalize it so a hard-coded user and pass isn't needed anymore. | + | That's to run a slave on your machine. To actually add it to the system, I need to give you a user and password and do some work on the buildmaster. Also, as noted in the buildbot.tac file, please don't commit your buildslave directory after you create your slave. It's arguable whether or not this should even be in svn since it's just the generated files with some added comments. But don't commit it after you put your user and pass in it, because then the whole world can see it. Commit it after you generalize it so a hard-coded user and pass isn't needed anymore. |
To make a new buildFactory: | To make a new buildFactory: | ||
| + | <pre> | ||
svn co https://armagetronad.svn.sourceforge.net/svnroot/armagetronad/support/buildbot/buildmaster | svn co https://armagetronad.svn.sourceforge.net/svnroot/armagetronad/support/buildbot/buildmaster | ||
cd buildmaster | cd buildmaster | ||
vi master.cfg | vi master.cfg | ||
| + | </pre> | ||
Actually, I'd suggest using your regular code editor, which for me isn't vi. The file is a python source file, so you might have to set syntax highlighting manually. Test your config file with "python master.cfg". That's not a complete test, for a complete test you'll need to run a buildmaster, but don't sweat it. Just worry about adding your buildFactory and/or tweaking existing buildFactories, and test it for syntax errors with the python interpreter. | Actually, I'd suggest using your regular code editor, which for me isn't vi. The file is a python source file, so you might have to set syntax highlighting manually. Test your config file with "python master.cfg". That's not a complete test, for a complete test you'll need to run a buildmaster, but don't sweat it. Just worry about adding your buildFactory and/or tweaking existing buildFactories, and test it for syntax errors with the python interpreter. | ||
Obviously to get it going live you need to tell me so I can update the buildmaster with the new config file. | Obviously to get it going live you need to tell me so I can update the buildmaster with the new config file. | ||
Revision as of 08:56, 11 January 2007
To add a slave:
- Install python (can't build arma without it anyway, duh)
- Install twisted
- Install buildbot (buildmaster is 0.75, portage has 0.74, don't know if that's a problem or not)
svn co https://armagetronad.svn.sourceforge.net/svnroot/armagetronad/support/buildbot/buildslavecd buildslavevi buildbot.tac- Change password, username, and the other thing (root directory)
make start
That's to run a slave on your machine. To actually add it to the system, I need to give you a user and password and do some work on the buildmaster. Also, as noted in the buildbot.tac file, please don't commit your buildslave directory after you create your slave. It's arguable whether or not this should even be in svn since it's just the generated files with some added comments. But don't commit it after you put your user and pass in it, because then the whole world can see it. Commit it after you generalize it so a hard-coded user and pass isn't needed anymore.
To make a new buildFactory:
svn co https://armagetronad.svn.sourceforge.net/svnroot/armagetronad/support/buildbot/buildmaster cd buildmaster vi master.cfg
Actually, I'd suggest using your regular code editor, which for me isn't vi. The file is a python source file, so you might have to set syntax highlighting manually. Test your config file with "python master.cfg". That's not a complete test, for a complete test you'll need to run a buildmaster, but don't sweat it. Just worry about adding your buildFactory and/or tweaking existing buildFactories, and test it for syntax errors with the python interpreter.
Obviously to get it going live you need to tell me so I can update the buildmaster with the new config file.
