Meego Wiki
Views

SDK/External Build Host

From MeeGo wiki
< SDK(Difference between revisions)
Jump to: navigation, search
(→People behind this host)
(→Git repositories)
 
(16 intermediate revisions not shown)
Line 1: Line 1:
-
= External build hosts at OSU =
 
-
 
For purposes outside the current OBS implementation external build host series were established in OSU.
For purposes outside the current OBS implementation external build host series were established in OSU.
-
* sdkbuild.in.meego.com
+
* sdkbuild.in.meego.com (frontend build host)
 +
* sdkmac.in.meego.com (real Mac OS X Snow Leopard host)
== Toolchains ==
== Toolchains ==
Line 9: Line 8:
* master (currently, MeeGo 1.2)
* master (currently, MeeGo 1.2)
* harmattan
* harmattan
 +
 +
=== Git repositories ===
 +
 +
* toolchains source code: git://sdkbuild.in.meego.com/git/toolchains.git
 +
* buildbot configuration: git://sdkbuild.in.meego.com/git/buildbot.git
 +
 +
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/
=== Master buildbot instance ===
=== Master buildbot instance ===
-
Main web frontend: http://sdkbuild.meego.com/toolchains
 
  BB_NUMBER[0]=0
  BB_NUMBER[0]=0
  BB_NAME[0]="Meego/Maemo SDK Toolchains Master"
  BB_NAME[0]="Meego/Maemo SDK Toolchains Master"
Line 20: Line 29:
  BB_PREFIXCMD[0]=""
  BB_PREFIXCMD[0]=""
-
=== Slave buildbot instances ===
+
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/
-
* toolchain32-lenny (local buildbot crontab)
 
-
@reboot schroot -r -c toolchain32 buildbot start /var/lib/buildbot/toolchains/lenny32
 
-
* toolchain64-lenny (local buildbot crontab)
 
-
@reboot schroot -r -c toolchain64 buildbot start /var/lib/buildbot/toolchains/lenny64
 
-
* toolchain-macos: ''real Mac OS host currently missing''
 
=== Slave buildbot instances ===
=== Slave buildbot instances ===
-
* toolchain32-lenny (local buildbot crontab)
+
* toolchain32-lenny, used for mingw32 builds as well (buildbot's crontab on sdkbuild)
  @reboot schroot -r -c toolchain32 buildbot start /var/lib/buildbot/toolchains/lenny32
  @reboot schroot -r -c toolchain32 buildbot start /var/lib/buildbot/toolchains/lenny32
-
* toolchain64-lenny (local buildbot crontab)
+
* toolchain64-lenny (buildbot's crontab on sdkbuild)
  @reboot schroot -r -c toolchain64 buildbot start /var/lib/buildbot/toolchains/lenny64
  @reboot schroot -r -c toolchain64 buildbot start /var/lib/buildbot/toolchains/lenny64
-
* toolchain-macos: ''real Mac OS host currently missing''
+
* toolchain-macos (on sdkmac)
-
=== Git repositories ===
+
== Tunneling Tips ==
-
* toolchains source code: git://sdkbuild.in.meego.com/git/toolchains.git
+
''This implies you have an account on access.meego.com.''
-
* buildbot configuration: git://sdkbuild.in.meego.com/git/buildbot.git
+
-
 
+
-
See also [[#Tunneling Tips]].
+
-
 
+
-
= Tunneling Tips =
+
-
 
+
-
''This implies you have an account in access.meego.com.''
+
-
If you are in a private network behind a HTTP proxy, you have to use another tunnel in your .ssh/config:
+
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
  Host *.meego.com
  ProxyCommand corkscrew 172.16.42.42 8080 %h %p
  ProxyCommand corkscrew 172.16.42.42 8080 %h %p
-
Since sdkbuild.in.meego.com is connected to a private network, you have to use another tunnel in your .ssh/config:
+
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
  Host sdkbuild.in.meego.com
  ProxyCommand ssh access.meego.com nc %h %p
  ProxyCommand ssh access.meego.com nc %h %p
-
To get access to git-daemon available on sdkbuild.in.meego.com for push/fetch, create a tunnel:
+
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
  ssh -N -f -L 9418:localhost:9418 sdkbuild.in.meego.com
and then use git://localhost/git/toolchains.git as URL.
and then use git://localhost/git/toolchains.git as URL.
-
= People behind these hosts =
+
== People behind these hosts ==
* Al Nikolov <al.nikolov@nokia.com>
* Al Nikolov <al.nikolov@nokia.com>
 +
 +
[[Category:SDK]]

Latest revision as of 13:50, 1 September 2011

For purposes outside the current OBS implementation external build host series were established in OSU.

  • sdkbuild.in.meego.com (frontend build host)
  • sdkmac.in.meego.com (real Mac OS X Snow Leopard host)

Contents

Toolchains

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:

  • master (currently, MeeGo 1.2)
  • harmattan

Git repositories

  • toolchains source code: git://sdkbuild.in.meego.com/git/toolchains.git
  • buildbot configuration: git://sdkbuild.in.meego.com/git/buildbot.git

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/

Master buildbot instance 

BB_NUMBER[0]=0
BB_NAME[0]="Meego/Maemo SDK Toolchains Master"
BB_USER[0]="buildbot"
BB_BASEDIR[0]="/var/lib/buildbot/toolchains/master"
BB_OPTIONS[0]=""
BB_PREFIXCMD[0]=""

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/

Slave buildbot instances

  • toolchain32-lenny, used for mingw32 builds as well (buildbot's crontab on sdkbuild) 
@reboot schroot -r -c toolchain32 buildbot start /var/lib/buildbot/toolchains/lenny32
  • toolchain64-lenny (buildbot's crontab on sdkbuild) 
@reboot schroot -r -c toolchain64 buildbot start /var/lib/buildbot/toolchains/lenny64
  • toolchain-macos (on sdkmac)

Tunneling Tips

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.

People behind these hosts

  • Al Nikolov <al.nikolov@nokia.com>
Retrieved from "http://wiki.meego.com/SDK/External_Build_Host"
Personal tools