Skip to content
This repository has been archived by the owner on Apr 3, 2020. It is now read-only.

Buildbot

Jump to bottom
Halton Huo edited this page Aug 16, 2013 · 17 revisions

Build Infrastructure

  • Build infrastructure is composed of trying bot and build bot.
  • Trying bot will cover linting, compiling and essential test cases, the purpose is to provide reviewer information beyond code.
  • Build bot will cover full test, the purpose is to detect regression.
  • Code is hosted at https://github.com/otcshare/build-infrastructure, current working branch 1469_work.

Trying bot

Host name/IP                  | Role            | GUI    | How to start
------------------------------|-----------------|--------|-----------------------------------------------
| wrtvms.bj.intel.com         | VMWare server   | vSphere| N/A
| wrt-buildbot.bj.intel.com   | Trybot master   | VNC    | cd ~/masters/master.tryserver.wrt && make restart
| 10.240.192.170              | xwalk_linux     | VNC    | cd ~/build/ubuntu-try-1/build-infrastructure/slave && ./run_linux_try.sh ubuntu-try-1 for Crosswalk. 
|                             | content_linux   | VNC    | cd ~/build/ubuntu-try-11/build-infrastructure/slave, ./run_linux_try.sh ubuntu-try-11
| 10.240.192.172              | xwalk_linux     | VNC    | cd ~/build/ubuntu-try-2/build-infrastructure/slave && ./run_linux_try.sh ubuntu-try-2
|                             | content_linux   | VNC    | cd ~/build/ubuntu-try-12/build-infrastructure/slave && ./run_linux_try.sh ubuntu-try-12
| 10.240.192.171              | xwalk_win       | RDP    | In D:\build-infrastructure\slave, click run_win_try1.bat 
| 10.240.192.173              | xwalk_win       | RDP    | In D:\build-infrastructure\slave, click run_win_try2.bat
| 10.240.192.181              | content_win     | RDP    | In D:\build-infrastructure\slave, click run_win_try11.bat 
| 10.240.192.183              | content_win     | RDP    | In D:\build-infrastructure\slave, click run_win_try12.bat
| 10.240.192.174              | content_android | VNC    | cd ~/build/android-try-12/build-infrastructure/slave && ./run_linux_try.sh android-try-11

Build bot

Host name                                  | Role                | GUI    | How to start
-------------------------------------------|---------------------|--------|-----------------------------------------------
| wrtvms.sh.intel.com                      | VMWare server       | vSphere| N/A
| wrt-build.sh.intel.com                   | Buildbot master     | VNC    | cd ~/masters/master.wrt && make restart
| builder-ubuntu1.sh.intel.com             | dev-wrt-linux       | VNC    | cd ~/build/wrt-ubuntu-builder/build-infrastructure/slave && ./run_dev_wrt_linux_build.sh
|                                          | dev-content-linux   |        | cd ~/build/content-ubuntu-builder/build-infrastructure/slave && ./run_dev_content_linux_build.sh
| builder-ubuntu32-1.sh.intel.com          | dev-wrt-linux32     | VNC    | cd ~/build/wrt-ubuntu32-builder/build-infrastructure/slave && ./run_dev_wrt_linux32_build.sh
|                                          | dev-content-linux32 |        | cd ~/build/content-ubuntu32-builder/build-infrastructure/slave && ./run_dev_content_linux_build.sh
| builder-win1.sh.intel.com(10.239.97.235) | dev-wrt-win         | RDP    | In D:\build-infrastructure\slave, click run_dev_wrt_win_build.bat
| builder-win2.sh.intel.com(10.239.97.236) | dev-content-win     | RDP    | In D:\build-infrastructure\slave, click run_dev_content_win_build.bat
| builder-android1.sh.intel.com            | dev-content-android | VNC    | cd ~/build/content-android-builder/build-infrastructure/slave && ./run_dev_content_android_build.sh
|                                          | dev-wrt-android     | VNC    | cd ~/build/wrt-android-builder/build-infrastructure/slave && ./run_dev_wrt_android_build.sh
| builder-aura1.sh.intel.com               | dev-wrt-aura        | VNC    | cd ~/build/wrt-aura-builder/build-infrastructure/slave && ./run_dev_wrt_aura_build.sh
| builder-tizen1.sh.intel.com              | dev-wrt-tizen       | VNC    | cd ~/build/wrt-tizen-builder/build-infrastructure/slave && ./run_dev_wrt_tizen_build.sh

Guidlines&Suggestions

  1. OS disk should be separated with slave disk
  • OS disk contains OS plus build required tools, better be located at /vmfs/volumes/storage/ (this is a 1T raid1 disks)
  • Slave disk contains build directory(build-infrastructure, depot_tools), better be located at /vmfs/volumes/ssd-raid0/ (because ssd disks idealy has better access time, which satisfy chromium huge code base)
  1. One VM -> One OS disk -> Multiple slave disks (depend on how many slaves you want to deploy on one VM)
  2. Shutdown VM if you want to copy some disk file.

BKMs

How to add a new VM

  1. Login wrtvms.bj.intel.com via vSphere client (if not install, get it from https://wrtvms.bj.intel.com/)
  2. Right click the server name(wrtvms.bj.intel.com) -> New Virtual Machine
  • OS size: Linux: 10GB, windows: 40GB
  • VM location: /vmfs/volumes/storage/<your_vm_name>
  1. Setup build environment by following Build-Crosswalk
  2. More easy way: copy existing VM OS disk will be very easy. For eg, if you want to create a new VM with Win8 SDK with VM name buildbot-slave-win100
ssh root@wrtvms.bj.intel.com
cd /vmfs/volumes/storage/buildbot-slave-win100
cp /vmfs/volumes/storage/buildbot-slave-win2/Win7OS.vmdk .
cp /vmfs/volumes/storage/buildbot-slave-win2/Win7OS-flat.vmdk .
edit the .vmx file, correct the OS filename or rename the copied vmdk
Clone this wiki locally