Buildbot - Revision history

Unknown user: /* Confirming Installation */

2020-10-07T19:30:21Z

Confirming Installation

← Older revision		Revision as of 19:30, 7 October 2020
Line 97:		Line 97:
	and then ran:		and then ran:

	<~~source~~>		<pre>
	$ buildbot --version		$ buildbot --version
	Buildbot version: 0.8.3p1		Buildbot version: 0.8.3p1
Line 105:		Line 105:
	Buildslave version: 0.8.3		Buildslave version: 0.8.3
	Twisted version: 11.0.0		Twisted version: 11.0.0
	</~~source~~>		</pre>

	=Creating Buildbots=		=Creating Buildbots=

Unknown user: /* Creating a Master */

2020-10-07T19:30:04Z

Creating a Master

← Older revision		Revision as of 19:30, 7 October 2020
Line 113:		Line 113:
	First, create the build master with the create-master command:		First, create the build master with the create-master command:

	<~~source~~>		<pre>
	$ cd /path/to/buildbot/stuff/		$ cd /path/to/buildbot/stuff/
	$ buildbot create-master master		$ buildbot create-master master
	</~~source~~>		</pre>

	This makes a directory called "master".		This makes a directory called "master".
Line 124:		Line 124:
	If you're looking for instant gratification, just do this:		If you're looking for instant gratification, just do this:

	<~~source~~>		<pre>
	$ mv master/master.cfg.sample master/master.cfg		$ mv master/master.cfg.sample master/master.cfg
	</~~source~~>		</pre>

	This will use an example git repository for the pyflakes project. However, since I was running on a system that already had a Buildbot running on it, and I just wanted to leave it alone and use my own, I had to change the default HTTP port (8010) to something else, and change the build slave port (9989) to something else.		This will use an example git repository for the pyflakes project. However, since I was running on a system that already had a Buildbot running on it, and I just wanted to leave it alone and use my own, I had to change the default HTTP port (8010) to something else, and change the build slave port (9989) to something else.
Line 132:		Line 132:
	Third, start the build master:		Third, start the build master:

	<~~source~~>		<pre>
	buildbot start master		buildbot start master
	</~~source~~>		</pre>

	(or, if you are not in the same directory as your buildbot master directory,)		(or, if you are not in the same directory as your buildbot master directory,)

	<~~source~~>		<pre>
	buildbot start /path/to/master		buildbot start /path/to/master
	</~~source~~>		</pre>

	You should see something like this:		You should see something like this:

	<~~source~~>		<pre>
	$ buildbot start master		$ buildbot start master
	Following twistd.log until startup finished..		Following twistd.log until startup finished..
Line 173:		Line 173:
	2011-06-03 16:20:09-0600 [-] configuration update complete		2011-06-03 16:20:09-0600 [-] configuration update complete
	The buildmaster appears to have (re)started correctly.		The buildmaster appears to have (re)started correctly.
	</~~source~~>		</pre>

	See [[#Errors]] below for error messages and resolution.		See [[#Errors]] below for error messages and resolution.

Unknown user: /* Creating a Sheep */

2020-10-07T19:29:35Z

Creating a Sheep

← Older revision		Revision as of 19:29, 7 October 2020
Line 185:		Line 185:
	You can create the build slave by running:		You can create the build slave by running:

	<~~source~~>		<pre>
	$ buildslave create-slave slave localhost:PPPP example-slave pass		$ buildslave create-slave slave localhost:PPPP example-slave pass
	</~~source~~>		</pre>

	which should give the output:		which should give the output:

	<~~source~~>		<pre>
	$ buildslave create-slave slave localhost:PPPP example-slave pass		$ buildslave create-slave slave localhost:PPPP example-slave pass
	mkdir /uufs/chpc.utah.edu/common/home/u0552682/codes/buildbot/slave		mkdir /uufs/chpc.utah.edu/common/home/u0552682/codes/buildbot/slave
Line 201:		Line 201:
	Please edit the files in /uufs/chpc.utah.edu/common/home/u0552682/codes/buildbot/slave/info appropriately.		Please edit the files in /uufs/chpc.utah.edu/common/home/u0552682/codes/buildbot/slave/info appropriately.
	buildslave configured in /uufs/chpc.utah.edu/common/home/u0552682/codes/buildbot/slave		buildslave configured in /uufs/chpc.utah.edu/common/home/u0552682/codes/buildbot/slave
	</~~source~~>		</pre>

	Second, start the build slave:		Second, start the build slave:

	<~~source lang="bash"~~>		<pre>
	buildslave start slave		buildslave start slave
	</~~source~~>		</pre>

	(or, if you are not in the same directory as your buildbot slave,)		(or, if you are not in the same directory as your buildbot slave,)

	<~~source~~>		<pre>
	buildslave start /path/to/slave		buildslave start /path/to/slave
	</~~source~~>		</pre>

	which should return the output:		which should return the output:

	<~~source~~>		<pre>
	$ buildslave start slave		$ buildslave start slave
	Following twistd.log until startup finished..		Following twistd.log until startup finished..
Line 227:		Line 227:
	2011-06-03 22:39:28-0600 [Broker,client] message from master: attached		2011-06-03 22:39:28-0600 [Broker,client] message from master: attached
	The buildslave appears to have (re)started correctly.		The buildslave appears to have (re)started correctly.
	</~~source~~>		</pre>

	==Webpage View==		==Webpage View==

Unknown user: /* Conceptualization of Configure Files */

2020-10-07T19:29:07Z

Conceptualization of Configure Files

← Older revision		Revision as of 19:29, 7 October 2020
Line 278:		Line 278:
	[[Image:GraphvizViz.png\|500px]]		[[Image:GraphvizViz.png\|500px]]

	<~~source~~>		<pre>
	digraph G {		digraph G {
	"Master Configuration File" -> "Scheduler"		"Master Configuration File" -> "Scheduler"
Line 303:		Line 303:
	"Associated BuildSlaves" -> "Builder4" -> "BuildFactory4" -> "Build4"		"Associated BuildSlaves" -> "Builder4" -> "BuildFactory4" -> "Build4"
	}		}
	</~~source~~>		</pre>

	In words:		In words:

Unknown user: /* Running Buildbot */

2020-10-07T19:28:51Z

Running Buildbot

← Older revision		Revision as of 19:28, 7 October 2020
Line 418:		Line 418:
	It is a good idea to make sure the Buildbot is stopped if you are changing the configuration file. Stop the buildbot by running:		It is a good idea to make sure the Buildbot is stopped if you are changing the configuration file. Stop the buildbot by running:

	<~~source lang="bash"~~>		<pre>
	buildbot stop master		buildbot stop master
	</~~source~~>		</pre>

	and edit master.cfg to use non-standard ports (not 8010 and not 9989).		and edit master.cfg to use non-standard ports (not 8010 and not 9989).
Line 426:		Line 426:
	Next, start the buildbot again:		Next, start the buildbot again:

	<~~source lang="bash"~~>		<pre>
	buildbot start master		buildbot start master
	</~~source~~>		</pre>

	==Reconfiguring==		==Reconfiguring==

Unknown user at 19:28, 7 October 2020

2020-10-07T19:28:19Z

← Older revision		Revision as of 19:28, 7 October 2020
Line 36:		Line 36:
	I installed the Buildbot master by running		I installed the Buildbot master by running

	<~~source~~>		<pre>
	$ python setup.py build		$ python setup.py build
	</~~source~~>		</pre>

	The next thing I had to do was add the future installation directory to my <code>$PYTHONPATH</code> variable (otherwise the python installer throws an error). I put this in one of my [[Dot files]] (.bashrc):		The next thing I had to do was add the future installation directory to my <code>$PYTHONPATH</code> variable (otherwise the python installer throws an error). I put this in one of my [[Dot files]] (.bashrc):

	<~~source~~>		<pre>
	export PYTHONPATH="${HOME}/pkg/buildbot/0.8.3_master/lib/python2.7/site-packages:${PYTHONPATH}"		export PYTHONPATH="${HOME}/pkg/buildbot/0.8.3_master/lib/python2.7/site-packages:${PYTHONPATH}"
	</~~source~~>		</pre>

	then made the directory:		then made the directory:

	<~~source~~>		<pre>
	$ mkdir -p ${HOME}/pkg/buildbot/0.8.3_master/lib/python2.7/site-packages		$ mkdir -p ${HOME}/pkg/buildbot/0.8.3_master/lib/python2.7/site-packages
	</~~source~~>		</pre>

	and then ran setup's installer:		and then ran setup's installer:

	<~~source~~>		<pre>
	$ python setup.py install --prefix=${HOME}/pkg/buildbot/0.8.3_master		$ python setup.py install --prefix=${HOME}/pkg/buildbot/0.8.3_master
	</~~source~~>		</pre>

	===Sheep===		===Sheep===
Line 64:		Line 64:
	Then I ran:		Then I ran:

	<~~source~~>		<pre>
	$ python setup.py build		$ python setup.py build
	</~~source~~>		</pre>

	Then I added the path to the Python package to my <code>$PYTHONPATH</code> variable:		Then I added the path to the Python package to my <code>$PYTHONPATH</code> variable:

	<~~source~~>		<pre>
	export PYTHONPATH="${HOME}/pkg/buildbot/0.8.3_slave/lib/python2.7/site-packages:${PYTHONPATH}"		export PYTHONPATH="${HOME}/pkg/buildbot/0.8.3_slave/lib/python2.7/site-packages:${PYTHONPATH}"
	</~~source~~>		</pre>

	then made the directory:		then made the directory:

	<~~source~~>		<pre>
	$ mkdir -p ${HOME}/pkg/buildbot/0.8.3_slave/lib/python2.7/site-packages		$ mkdir -p ${HOME}/pkg/buildbot/0.8.3_slave/lib/python2.7/site-packages
	</~~source~~>		</pre>

	and then ran setup's installer:		and then ran setup's installer:

	<~~source~~>		<pre>
	$ python setup.py install --prefix=${HOME}/pkg/buildbot/0.8.3_slave		$ python setup.py install --prefix=${HOME}/pkg/buildbot/0.8.3_slave
	</~~source~~>		</pre>

	===Confirming Installation===		===Confirming Installation===
Line 90:		Line 90:
	Once both installs finished, I added both to my path:		Once both installs finished, I added both to my path:

	<~~source~~>		<pre>
	export PATH="${HOME}/pkg/buildbot/0.8.3_master/bin:${PATH}"		export PATH="${HOME}/pkg/buildbot/0.8.3_master/bin:${PATH}"
	export PATH="${HOME}/pkg/buildbot/0.8.3_slave/bin:${PATH}"		export PATH="${HOME}/pkg/buildbot/0.8.3_slave/bin:${PATH}"
	</~~source~~>		</pre>

	and then ran:		and then ran:

Admin: /* Conceptualization of Configure Files */

2018-08-05T03:39:17Z

Conceptualization of Configure Files

← Older revision		Revision as of 03:39, 5 August 2018
Line 275:		Line 275:

	Documentation on configuration files: http://buildbot.net/buildbot/docs/current/Configuration.html#Configuration		Documentation on configuration files: http://buildbot.net/buildbot/docs/current/Configuration.html#Configuration

			[[Image:GraphvizViz.png\|500px]]

	<source>		<source>

Admin: /* Conceptualization of Configure Files */

2018-08-05T03:37:13Z

Conceptualization of Configure Files

← Older revision		Revision as of 03:37, 5 August 2018
Line 276:		Line 276:
	Documentation on configuration files: http://buildbot.net/buildbot/docs/current/Configuration.html#Configuration		Documentation on configuration files: http://buildbot.net/buildbot/docs/current/Configuration.html#Configuration

	<~~graphviz~~>		<source>
	digraph G {		digraph G {
	"Master Configuration File" -> "Scheduler"		"Master Configuration File" -> "Scheduler"
Line 301:		Line 301:
	"Associated BuildSlaves" -> "Builder4" -> "BuildFactory4" -> "Build4"		"Associated BuildSlaves" -> "Builder4" -> "BuildFactory4" -> "Build4"
	}		}
	</~~graphviz~~>		</source>

	In words:		In words:
Line 314:		Line 314:

	The Builder uses a BuildFactory to specify the steps involved in the Build.		The Builder uses a BuildFactory to specify the steps involved in the Build.



	==Project Source Code==		==Project Source Code==

Admin: /* Creating a Slave */

2018-08-05T03:34:34Z

Creating a Slave

← Older revision		Revision as of 03:34, 5 August 2018
Line 177:		Line 177:
	See [[#Errors]] below for error messages and resolution.		See [[#Errors]] below for error messages and resolution.

	==Creating a ~~Slave~~==		==Creating a Sheep==

	To create the build slave, you'll need some information from master.cfg:		To create the build slave, you'll need some information from master.cfg:
Line 185:		Line 185:
	You can create the build slave by running:		You can create the build slave by running:

	<~~pre~~>		<source>
	$ buildslave create-slave slave localhost:PPPP example-slave pass		$ buildslave create-slave slave localhost:PPPP example-slave pass
	</~~pre~~>		</source>

	which should give the output:		which should give the output:

	<~~pre~~>		<source>
	$ buildslave create-slave slave localhost:PPPP example-slave pass		$ buildslave create-slave slave localhost:PPPP example-slave pass
	mkdir /uufs/chpc.utah.edu/common/home/u0552682/codes/buildbot/slave		mkdir /uufs/chpc.utah.edu/common/home/u0552682/codes/buildbot/slave
Line 201:		Line 201:
	Please edit the files in /uufs/chpc.utah.edu/common/home/u0552682/codes/buildbot/slave/info appropriately.		Please edit the files in /uufs/chpc.utah.edu/common/home/u0552682/codes/buildbot/slave/info appropriately.
	buildslave configured in /uufs/chpc.utah.edu/common/home/u0552682/codes/buildbot/slave		buildslave configured in /uufs/chpc.utah.edu/common/home/u0552682/codes/buildbot/slave
	</~~pre~~>		</source>

	Second, start the build slave:		Second, start the build slave:
Line 211:		Line 211:
	(or, if you are not in the same directory as your buildbot slave,)		(or, if you are not in the same directory as your buildbot slave,)

	<~~pre~~>		<source>
	buildslave start /path/to/slave		buildslave start /path/to/slave
	</~~pre~~>		</source>

	which should return the output:		which should return the output:

	<~~pre~~>		<source>
	$ buildslave start slave		$ buildslave start slave
	Following twistd.log until startup finished..		Following twistd.log until startup finished..
Line 227:		Line 227:
	2011-06-03 22:39:28-0600 [Broker,client] message from master: attached		2011-06-03 22:39:28-0600 [Broker,client] message from master: attached
	The buildslave appears to have (re)started correctly.		The buildslave appears to have (re)started correctly.
	</~~pre~~>		</source>

	==Webpage View==		==Webpage View==

Admin: /* Creating a Master */

2018-08-05T03:33:56Z

Creating a Master

← Older revision		Revision as of 03:33, 5 August 2018
Line 113:		Line 113:
	First, create the build master with the create-master command:		First, create the build master with the create-master command:

	<source ~~lang="bash"~~>		<source>
	$ cd /path/to/buildbot/stuff/		$ cd /path/to/buildbot/stuff/
	$ buildbot create-master master		$ buildbot create-master master
Line 124:		Line 124:
	If you're looking for instant gratification, just do this:		If you're looking for instant gratification, just do this:

	<source ~~lang="bash"~~>		<source>
	$ mv master/master.cfg.sample master/master.cfg		$ mv master/master.cfg.sample master/master.cfg
	</source>		</source>
Line 132:		Line 132:
	Third, start the build master:		Third, start the build master:

	<source ~~lang="bash"~~>		<source>
	buildbot start master		buildbot start master
	</source>		</source>
Line 138:		Line 138:
	(or, if you are not in the same directory as your buildbot master directory,)		(or, if you are not in the same directory as your buildbot master directory,)

	<~~pre~~>		<source>
	buildbot start /path/to/master		buildbot start /path/to/master
	</~~pre~~>		</source>

	You should see something like this:		You should see something like this:

	<~~pre~~>		<source>
	$ buildbot start master		$ buildbot start master
	Following twistd.log until startup finished..		Following twistd.log until startup finished..
Line 173:		Line 173:
	2011-06-03 16:20:09-0600 [-] configuration update complete		2011-06-03 16:20:09-0600 [-] configuration update complete
	The buildmaster appears to have (re)started correctly.		The buildmaster appears to have (re)started correctly.
	</~~pre~~>		</source>

	See [[#Errors]] below for error messages and resolution.		See [[#Errors]] below for error messages and resolution.