Build slave: Difference between revisions
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
http://en.wikipedia.org/wiki/Continuous_integration#Automate_the_build | |||
10 Steps to get a build slave working with the master at http://trac.alleg.net - this assumes u have build admin permission and can add your own platform to a build configuration http://trac.alleg.net/admin/bitten/configs. | 10 Steps to get a build slave working with the master at http://trac.alleg.net - this assumes u have build admin permission and can add your own platform to a build configuration http://trac.alleg.net/admin/bitten/configs. | ||
| Line 40: | Line 43: | ||
10) '''Extract''' http://build.alleg.net/BittenSlave-0.7dev_r805-py2.6.7z and move the egg into site-packages and the scripts to C:\Python26\Scripts - this is an unmodified copy of the build from edgewall svn linked here for your convenience. | 10) '''Extract''' http://build.alleg.net/BittenSlave-0.7dev_r805-py2.6.7z and move the egg into site-packages and the scripts to C:\Python26\Scripts - this is an unmodified copy of the build from edgewall svn linked here for your convenience. | ||
That should do it, run the batch script and watch it go. | |||
Latest revision as of 08:00, 1 August 2010
http://en.wikipedia.org/wiki/Continuous_integration#Automate_the_build
10 Steps to get a build slave working with the master at http://trac.alleg.net - this assumes u have build admin permission and can add your own platform to a build configuration http://trac.alleg.net/admin/bitten/configs.
you need to at least do the following for the simplest recipe @ http://trac.alleg.net/build/ (1.1 Only) - the other more involved recipes are outside the scope of this article
1) Create a folder on your slave host called C:\build
2) From C:\build> svn co http://trac.alleg.net/svn/branch/FAZR6 to the folder you just made.
3) If you named C:\build something else besides what was instructed in step 1, start over.
You should now have C:\build\FAZR6\ with a bunch of crap in it.
4) Copy the C:\build\FAZR6\build\bitten.bat to somewhere handy on your host (like the desktop)
5) Edit it to add your slave name ex. --name stripe where it calls bitten-slave.
6) Also adjust the path to your vcvars bat if necessary (the line above)
You should have a bat script that looks kinda like this, I bolded thae parts you probably need to change/add:
rem #Imago <imagotrigger@gmail.com> - Runs the bitten slave on a host
- wut
call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvarsall.bat" x86
call C:\Python26\Scripts\bitten-slave --name test0 -f C:\build\FAZR6\update\bitten.ini -i 120 --log=C:\bitten-Allegiance.log http://trac.alleg.net/builds
goto wut
7) Install Perl and the Perl modules ppm install Win32-AbsPath (for msbuild log parsing) and ppm install XML-RPC (for fail reporting) to make the recipe happy
8) Install 7-Zip to default location so your host can attach the build to trac /w less bandwisth
9) Install Python 2.6
10) Extract http://build.alleg.net/BittenSlave-0.7dev_r805-py2.6.7z and move the egg into site-packages and the scripts to C:\Python26\Scripts - this is an unmodified copy of the build from edgewall svn linked here for your convenience.
That should do it, run the batch script and watch it go.
