For purposes outside the current OBS implementation external build host series were established in OSU.
Builds MeeGo/Maemo cross-toolchains for Linux (x86/x86_64), Windows and MacOS X. Currently, only armv7hl target supported. Builds triggered by pushing commits to the toolchain git repository. Watched branches are:
See also #Tunneling Tips.
A Gitweb browsing interface: http://sdkbuild.meego.com/cgi-bin/gitweb.cgi
Read-only anonymous HTTP access is also available: http://sdkbuild.meego.com/git/
BB_NUMBER=0 BB_NAME="Meego/Maemo SDK Toolchains Master" BB_USER="buildbot" BB_BASEDIR="/var/lib/buildbot/toolchains/master" BB_OPTIONS="" BB_PREFIXCMD=""
Main web frontend: http://sdkbuild.meego.com/toolchains/
IRC bot: toolchains @ #meego-sdk-bb
For exceptional cases (eg. to repeat a build without pushing any new commits), use buildbot PBchange interface:
buildbot sendchange --username=myname --master=localhost:9989 --branch=master reasonwhy
Build artifacts: http://sdkbuild.meego.com/toolchains/result/
@reboot schroot -r -c toolchain32 buildbot start /var/lib/buildbot/toolchains/lenny32
@reboot schroot -r -c toolchain64 buildbot start /var/lib/buildbot/toolchains/lenny64
This implies you have an account on access.meego.com.
If you are in a private network behind a HTTP proxy, you have to get outside using an HTTP tunnel in your .ssh/config:
Host *.meego.com ProxyCommand corkscrew 172.16.42.42 8080 %h %p
Since sdkbuild.in.meego.com is connected to a private network, you have get inside using another tunnel in your .ssh/config:
Host sdkbuild.in.meego.com ProxyCommand ssh access.meego.com nc %h %p
And since other hosts are connected to another VLAN, you have to create fourth tunnel:
Host sdkmac.in.meego.com ProxyCommand ssh sdkbuild.in.meego.com nc %h %p
To get access to git-daemon available on sdkbuild.in.meego.com for push/fetch, create third tunnel:
ssh -N -f -L 9418:localhost:9418 sdkbuild.in.meego.com
and then use git://localhost/git/toolchains.git as URL.