github/CoolProp
1
1
Fork 0
mirror of https://github.com/CoolProp/CoolProp.git synced 2026-04-01 03:00:13 -04:00
Code Issues Packages Projects Releases Wiki Activity

Migrate buildbot docs to sphinx.

Browse Source 
Closes https://github.com/CoolProp/CoolProp/issues/156

Signed-off-by: Ian Bell <ian.h.bell@gmail.com>
This commit is contained in:
Ian Bell
2014-09-25 00:32:11 +02:00
parent 5c2bc9da00
commit e939e82657
2 changed files with 51 additions and 50 deletions
Download Patch File Download Diff File Expand all files Collapse all files

51
Web/develop/buildbot.rst
View File

@@ -3,6 +3,57 @@
Buildbot
********
Buildbot masters and slaves
===========================
Master
------
From the root of the git checkout (this will use the master.cfg from CoolProp)
```
pip install buildbot
cd dev/buildbot
buildbot create-master master
buildbot start master
```
The file ``buildbot-private.py`` (which is a python module with the passwords for the slaves as well as the buildbot website), should also be placed in the master folder next to master.cfg. Alternatively, you can put the ``buildbot_private.py`` in another folder on the master's computer and make a soft-link in the master folder to point to the buildbot_private.py file.
If you want to completely restart the master, you can do
```
buildbot restart master
```
but usually a
```
buildbot reconfig master
```
will do the job since it will just reparse the configuration file without signing you out of the server
To ensure that the buildbot server stays online, you can make a script with the contents
```
buildbot start /path/to/master_folder
```
and add it to a cron job
Slaves
------
To start a slave connected to a buildbot master at IP address 10.0.0.2 (default for host for VirtualBox), with a slave named ``example-slave`` and passsword ``pass``, run the command
```
buildslave create-slave slave 10.0.0.2:9989 example-slave pass
buildslave start slave
```
If the master is somewhere else, just change the IP address. As of Sept, 2014, the master was at www.coolprop.dreamhosters.com. The buildbot_private.py on the master holds the required passwords.
On linux, you can add the following lines to the end of your ``~/.profile`` file (similar ideas apply on other platforms) to autostart the slave when the user logs in:
```
# Connect to the buildbot master
buildslave start ~/slave
```
Setting MIME type handler
=========================

50
dev/buildbot/docs.md
View File

@@ -1,50 +0,0 @@
Buildbot masters and slaves
===========================
Master
------
From the root of the git checkout (this will use the master.cfg from CoolProp)
```
pip install buildbot
cd dev/buildbot
buildbot create-master master
buildbot start master
```
The file ``buildbot-private.py`` (which is a python module with the passwords for the slaves as well as the buildbot website), should also be placed in the master folder next to master.cfg. Alternatively, you can put the ``buildbot_private.py`` in another folder on the master's computer and make a soft-link in the master folder to point to the buildbot_private.py file.
If you want to completely restart the master, you can do
```
buildbot restart master
```
but usually a
```
buildbot reconfig master
```
will do the job since it will just reparse the configuration file without signing you out of the server
To ensure that the buildbot server stays online, you can make a script with the contents
```
buildbot start /path/to/master_folder
```
and add it to a cron job
Slaves
------
To start a slave connected to a buildbot master at IP address 10.0.0.2 (default for host for VirtualBox), with a slave named ``example-slave`` and passsword ``pass``, run the command
```
buildslave create-slave slave 10.0.0.2:9989 example-slave pass
buildslave start slave
```
If the master is somewhere else, just change the IP address.
On linux, you can add the following lines to the end of your ``~/.profile`` file (similar ideas apply on other platforms) to autostart the slave when the user logs in:
```
# Connect to the buildbot master
buildslave start ~/slave
```