Changes between Version 1 and Version 2 of Bitten Slave Daemon Windows

Timestamp:

Oct 24, 2009, 10:04:34 PM (15 years ago)

Author:

Sorin Sbarnea <sorin.sbarnea@…>

Comment:

--

Bitten Slave Daemon Windows

@@ -1 +1 @@
 = Configuring a Windows Bitten Slave =
 
-These steps should enable a bitten slave on windows for building and testing FiPy.
+These steps should enable a bitten slave on Windows.
 
- * Install pythonxy <http://www.pythonxy.com>
- * Install pysparse <http://pysparse.sf.net>
- * Go to the command line and type "{{{python}}}" and then type "{{{import pysparse}}}" and "{{{import numpy}}}" to check that everything is basically working.
+ * Install python, setuptools and bitten
  * Install bitten "{{{easy_install http://svn.edgewall.org/repos/bitten/trunk/}}}"
- * Create a "{{{bitten.ini}}}" file in a directory. Something like
-   {{{
-   [fipy]
-   inline=True
-   Trilinos=False
-   }}}
- * Execute the bitten command "{{{bitten-slave --verbose --config=bitten.ini --log=bitten.log http://www.matforge.org/fipy/builds}}}"
+ * Execute the bitten command "{{{bitten-slave --verbose --config=bitten.ini --log=bitten.log http://www.example.com/tract/project/builds}}}"
  * You should now have a working bitten slave. Of course, the bitten slave may go down periodically, like when you log off. To keep the slave running there are a number of options. Some involve creating a windows service, which I couldn't get working, but are probably better. An alternative is to just create a scheduled task. To start, create a python file "{{{bittenLaunch.py}}}" along side "{{{bitten.ini}}}" that simply relaunches the bitten slave if "{{{bitten-slave}}}" is not found with the "{{{tasklist}}}" command.
 {{{
@@ -26 +18 @@
           '--config=bitten.ini',
           '--log=bitten.log',
-          'http://www.matforge.org/fipy/builds']
+          'http://www.example.com/trac/project/builds']