BuildBot - Revision history

Jpye at 02:09, 23 April 2017

2017-04-23T02:09:49Z

← Older revision		Revision as of 02:09, 23 April 2017
Line 1:		Line 1:
	~~{{outdated}}~~

	''Our buildbot is now partly online (Apr 2017). When we resolve some outstanding DNS issues, we should be able to make it visible again.''		''Our buildbot is now partly online (Apr 2017). When we resolve some outstanding DNS issues, we should be able to make it visible again.''

Line 6:		Line 4:

	== Setting up a MinGW-w64 buildslave ==		== Setting up a MinGW-w64 buildslave ==

			{{outdated-section}}

	Follow the instructions for [[setting up a MinGW-w64 build environment]]. Then, broadly following [http://sourceforge.net/apps/trac/mingw-w64/wiki/Setup%20a%20MSYS%20Buildbot%20Slave these instructions], we suggest:		Follow the instructions for [[setting up a MinGW-w64 build environment]]. Then, broadly following [http://sourceforge.net/apps/trac/mingw-w64/wiki/Setup%20a%20MSYS%20Buildbot%20Slave these instructions], we suggest:

Jpye at 02:09, 23 April 2017

2017-04-23T02:09:11Z

← Older revision		Revision as of 02:09, 23 April 2017
Line 1:		Line 1:
	{{outdated}}		{{outdated}}

	''~~We will work on getting our~~ buildbot online again ~~as soon as possible~~''		''Our buildbot is now partly online (Apr 2017). When we resolve some outstanding DNS issues, we should be able to make it visible again.''

	The ASCEND BuildBot is currently up and running at http://build.ascend4.org/. If you have a reliable machine that you can contribute as a build-slave, please let us know!		The ASCEND BuildBot is currently up and running at http://build.ascend4.org/. If you have a reliable machine that you can contribute as a build-slave, please let us know!

Jpye at 02:10, 14 April 2015

2015-04-14T02:10:53Z

← Older revision		Revision as of 02:10, 14 April 2015
Line 1:		Line 1:
			{{outdated}}

			''We will work on getting our buildbot online again as soon as possible''

	The ASCEND BuildBot is currently up and running at http://build.ascend4.org/. If you have a reliable machine that you can contribute as a build-slave, please let us know!		The ASCEND BuildBot is currently up and running at http://build.ascend4.org/. If you have a reliable machine that you can contribute as a build-slave, please let us know!

Jpye at 09:04, 18 August 2013

2013-08-18T09:04:55Z

← Older revision		Revision as of 09:04, 18 August 2013
Line 49:		Line 49:
	PATH=.;C:\mingw\msys\local\bin;c:\mingw\64\bin;C:\mingw\msys\bin;c:\Windows\system32;c:\Windows;c:\Windows\System32\Wbem;c:\Windows\System32\WindowsPowerShell\v1.0\;c:\Program Files\SlikSvn\bin;c:\Python27;c:\Python27\Scripts		PATH=.;C:\mingw\msys\local\bin;c:\mingw\64\bin;C:\mingw\msys\bin;c:\Windows\system32;c:\Windows;c:\Windows\System32\Wbem;c:\Windows\System32\WindowsPowerShell\v1.0\;c:\Program Files\SlikSvn\bin;c:\Python27;c:\Python27\Scripts
	* Follow [http://stackoverflow.com/questions/305870/accessing-environment-variables-from-windows-services/2728574#2728574 these instructions] to add an 'Environment' key in your Buildbot service in regedit. On our system, we added <tt>HOME</tt>, <t>variables using this method (as shown below). We tried setting PATH here (which would have been nicer than a global user setting) but it didn't work.		* Follow [http://stackoverflow.com/questions/305870/accessing-environment-variables-from-windows-services/2728574#2728574 these instructions] to add an 'Environment' key in your Buildbot service in regedit. On our system, we added <tt>HOME</tt>, <t>variables using this method (as shown below). We tried setting PATH here (which would have been nicer than a global user setting) but it didn't work.
	HOME=C:/mingw/msys/home/buildslave		HOME=C:/mingw/msys/home/buildslave
	PATH=.;C:\mingw\msys\local\bin;c:\mingw\64\bin;C:\mingw\msys\bin;c:\Windows\system32;c:\Windows;c:\Windows\System32\Wbem;c:\Windows\System32\WindowsPowerShell\v1.0\;c:\Program Files\SlikSvn\bin;c:\Python27;c:\Python27\Scripts		OSTYPE=msys
	OSTYPE=msys

	''TODO'' figure out if there is a way to modify the <tt>buildbot_service.py</tt> so that a custom environment can be specified just for the buildslave.		''TODO'' figure out if there is a way to modify the <tt>buildbot_service.py</tt> so that a custom environment can be specified just for the buildslave.

Jpye at 08:58, 18 August 2013

2013-08-18T08:58:08Z

← Older revision		Revision as of 08:58, 18 August 2013
Line 39:		Line 39:
	* Right-click on the 'Buildbot' folder, click 'Permissions'. Add the user 'buildslave' and grant full permissions to that user.		* Right-click on the 'Buildbot' folder, click 'Permissions'. Add the user 'buildslave' and grant full permissions to that user.
	* Returning to the 'Services' tool, start the 'BuildBot' service. It is supposed to fail ''again'' at this stage, but in doing so will create a new parameter set that we can now edit.		* Returning to the 'Services' tool, start the 'BuildBot' service. It is supposed to fail ''again'' at this stage, but in doing so will create a new parameter set that we can now edit.
	* Back in <tt>regedit</tt>, naviate to 'Buildbot' and press <tt>F5</tt> to refresh the view. A new 'Parameters' sub-folder appears. Enter this 'Parameters' folder, then in the right pane, right-click and create new 'String value' named 'directories'. Double-click the resulting key, and enter its value as <tt>c:\mingw\msys\home\buildslave\win7-64</tt>		* Back in <tt>regedit</tt>, naviate to 'Buildbot' and press <tt>F5</tt> to refresh the view. A new 'Parameters' sub-folder appears. Enter this 'Parameters' folder, then in the right pane, right-click and create new 'String value' named 'directories'. Double-click the resulting key, and enter its value as '<tt>c:\mingw\msys\home\buildslave\win7-64</tt>'.
	* ''TODO'~~' figure~~ out how to set the ~~necessary~~ environment variables for ~~this~~ service, ~~including the~~ PATH.
	** Probably [http://stackoverflow.com/questions/305870/accessing-environment-variables-from-windows-services/2728574#2728574 ~~like~~ this].		The remaining job is to get the necessary environment variables set up for this service. In the case of a MinGW-w64 buildbot, this is a bit tricky, because normally the environment is set up nicely by <tt>bash</tt> when you enter your MSYS shell, but Buildbot is not running from inside <tt>bash</tt> (at least we can't work out yet how to do that). To take a snapshot of your MSYS environment, in a form suitable for pasting into a Windows dialog box etc, enter MSYS and type
			cmd
			env > myenv.txt
			exit
			There are two ways to set environment variables for <tt>buildslave</tt>:
			* In the start menu, type 'Environment, and select 'Edit environment variables for your account'. You can specify a <tt>PATH</tt> user variable here, and it will work well when the service starts (but you may need to restart the machine first). On our system, we set this to
			PATH=.;C:\mingw\msys\local\bin;c:\mingw\64\bin;C:\mingw\msys\bin;c:\Windows\system32;c:\Windows;c:\Windows\System32\Wbem;c:\Windows\System32\WindowsPowerShell\v1.0\;c:\Program Files\SlikSvn\bin;c:\Python27;c:\Python27\Scripts
			* Follow [http://stackoverflow.com/questions/305870/accessing-environment-variables-from-windows-services/2728574#2728574 these instructions] to add an 'Environment' key in your Buildbot service in regedit. On our system, we added <tt>HOME</tt>, <t>variables using this method (as shown below). We tried setting PATH here (which would have been nicer than a global user setting) but it didn't work.
			HOME=C:/mingw/msys/home/buildslave
			PATH=.;C:\mingw\msys\local\bin;c:\mingw\64\bin;C:\mingw\msys\bin;c:\Windows\system32;c:\Windows;c:\Windows\System32\Wbem;c:\Windows\System32\WindowsPowerShell\v1.0\;c:\Program Files\SlikSvn\bin;c:\Python27;c:\Python27\Scripts
			OSTYPE=msys

			''TODO'' figure out if there is a way to modify the <tt>buildbot_service.py</tt> so that a custom environment can be specified just for the buildslave.

	See also:		See also:

Jpye at 07:16, 18 August 2013

2013-08-18T07:16:43Z

← Older revision		Revision as of 07:16, 18 August 2013
Line 41:		Line 41:
	* Back in <tt>regedit</tt>, naviate to 'Buildbot' and press <tt>F5</tt> to refresh the view. A new 'Parameters' sub-folder appears. Enter this 'Parameters' folder, then in the right pane, right-click and create new 'String value' named 'directories'. Double-click the resulting key, and enter its value as <tt>c:\mingw\msys\home\buildslave\win7-64</tt>		* Back in <tt>regedit</tt>, naviate to 'Buildbot' and press <tt>F5</tt> to refresh the view. A new 'Parameters' sub-folder appears. Enter this 'Parameters' folder, then in the right pane, right-click and create new 'String value' named 'directories'. Double-click the resulting key, and enter its value as <tt>c:\mingw\msys\home\buildslave\win7-64</tt>
	* ''TODO'' figure out how to set the necessary environment variables for this service, including the PATH.		* ''TODO'' figure out how to set the necessary environment variables for this service, including the PATH.
			** Probably [http://stackoverflow.com/questions/305870/accessing-environment-variables-from-windows-services/2728574#2728574 like this].

	See also:		See also:

Jpye at 07:15, 18 August 2013

2013-08-18T07:15:05Z

@@ Line 26: / Line 26: @@
   buildslave start $BBSLAVEHOME/$BBSLAVENAME
-To get this running in a permanent way, however, you will want to install as a service. The suggested approach is...
+To get this running in a permanent way, however, you will want to install as a service. The suggested approach (following [http://trac.buildbot.net/wiki/RunningBuildbotOnWindows this guide]) is:
 See also:

Jpye at 06:30, 18 August 2013

2013-08-18T06:30:55Z

← Older revision		Revision as of 06:30, 18 August 2013
Line 17:		Line 17:
	export BBSLAVENAME=''name''		export BBSLAVENAME=''name''
	export BBSLAVEPW=''password''		export BBSLAVEPW=''password''
	export BBHOST=build.ascend4.org		export BBHOST=''build.ascend4.org''
	export BBPORT=''port number''		export BBPORT=''port number''
	mkdir -p $BBSLAVEHOME/$BBSLAVENAME		mkdir -p $BBSLAVEHOME/$BBSLAVENAME

Jpye at 06:29, 18 August 2013

2013-08-18T06:29:50Z

← Older revision		Revision as of 06:29, 18 August 2013
Line 1:		Line 1:
	The ASCEND BuildBot is currently up and running at http://build.ascend4.org/. If you have a reliable machine that you can contribute as a build-slave, please let us know!		The ASCEND BuildBot is currently up and running at http://build.ascend4.org/. If you have a reliable machine that you can contribute as a build-slave, please let us know!

			== Setting up a MinGW-w64 buildslave ==

			Follow the instructions for [[setting up a MinGW-w64 build environment]]. Then, broadly following [http://sourceforge.net/apps/trac/mingw-w64/wiki/Setup%20a%20MSYS%20Buildbot%20Slave these instructions], we suggest:

			* install [https://pypi.python.org/pypi/zope.interface zope.interface]. We used [https://pypi.python.org/packages/2.7/z/zope.interface/zope.interface-4.0.5.win-amd64-py2.7.exe zope.interface-4.0.5.win-amd64-py2.7.exe].
			* install [http://twistedmatrix.com/trac/wiki/Downloads#Windows Twisted 64-bit for Windows]. We used .exe version 13.1.0.
			* build and install BuildBot slave 0.8.7p1
			wget https://pypi.python.org/packages/source/b/buildbot-slave/buildbot-slave-0.8.7p1.tar.gz --no-check-certificate
			tar zxf buildbot-slave-0.8.7p1.tar.gz
			cd buildbot-slave-0.8.7p1
			python setup.py bdist_wininst
			start dist/buildbot-slave-0.8.7p1.win-amd64.exe
			* Setup the buildbot:
			export BBSLAVEHOME=/home/buildslave
			export BBSLAVENAME=''name''
			export BBSLAVEPW=''password''
			export BBHOST=build.ascend4.org
			export BBPORT=''port number''
			mkdir -p $BBSLAVEHOME/$BBSLAVENAME
			cd $BBSLAVEHOME/$BBSLAVENAME
			buildslave create-slave $BBSLAVEHOME/$BBSLAVENAME $BBHOST:$BBPORT $BBSLAVENAME $BBSLAVEPW

			You can run the slave manually, just to test it, using
			buildslave start $BBSLAVEHOME/$BBSLAVENAME

			To get this running in a permanent way, however, you will want to install as a service. The suggested approach is...

			See also:
			* http://trac.buildbot.net/wiki/RunningBuildbotOnWindows
			* http://www.mereidea.com/blog/2010/09/02/buildbot-slaves-as-a-windows-service-and-adding-a-testing-framework-unittest/

	[[Category:Development]]		[[Category:Development]]

Jpye at 08:04, 8 November 2011

2011-11-08T08:04:31Z

← Older revision		Revision as of 08:04, 8 November 2011
Line 1:		Line 1:
	~~{{missing}}~~		The ASCEND BuildBot is currently up and running at http://build.ascend4.org/. If you have a reliable machine that you can contribute as a build-slave, please let us know!

	~~'''~~The ASCEND BuildBot is currently ~~offline; we hope to restore it shortly~~.~~'''~~

	[[Category:Development]]		[[Category:Development]]