Pr docker factory travis ci test

.gitignore

@@ -50,7 +50,6 @@ coverage.xml
 *.pot
 
 # Django stuff:
-*.log
 local_settings.py
 
 # Sphinx documentation
@@ -73,3 +72,18 @@ results/
 
 # ctas
 TAGS
+tags
+
+# Alternate config files
+*.json
+
+# Apple foo
+.AppleDouble
+.DS_Store
+
+# Patch foo
+*.rej
+*.orig
+
+# geckodriver log
+geckodriver.log

.jenkinsfile

@@ -0,0 +1,40 @@
+def changeBranch = "change-${GERRIT_CHANGE_NUMBER}-${GERRIT_PATCHSET_NUMBER}"
+
+pipeline {
+    agent { label 'boardfarm' }
+
+    stages {
+        stage('checkout gerrit change') {
+            steps {
+                // TODO: don't hardcode user name
+                git url: 'ssh://[email protected]:29418/lgirdk/boardfarm'
+                sh "git fetch origin ${GERRIT_REFSPEC}:${changeBranch}"
+                sh "git rebase --abort || true"
+                sh "git reset --hard HEAD"
+                sh "git checkout ${changeBranch}"
+                sh "git rebase origin/master"
+            }
+        }
+        stage('run bft test') {
+            steps {
+                ansiColor('xterm') {
+                    sh 'git show HEAD'
+                    sh 'pip install --user -r requirements.txt'
+                    sh 'yes | BFT_DEBUG=y ./bft -b qemux86-openwrt -r http://c4.lgirdk.com/~mattsm/openwrt-x86-generic-combined-ext4.vmdk -y -x travisci'
+                    sh 'grep tests_fail...0, results/test_results.json'
+                }
+            }
+        }
+        stage('post results to gerrit') {
+            steps {
+                sh '''#!/bin/bash
+                    cat results/test_results.json | jq '.test_results[] | [ .grade, .name, .message, .elapsed_time ] | @tsv' | \
+                        sed -e 's/"//g' -e 's/\\t/    /g' | \
+                        while read -r line; do
+                                echo $line >> message
+                        done
+                        '''
+            }
+        }
+    }
+}

.travis.yml

@@ -0,0 +1,24 @@
+dist: trusty
+sudo: required
+language: python
+python:
+        - "2.7"
+before_install:
+        - sudo apt-get -qq update
+        - sudo apt-get remove docker docker-engine docker.io
+        - sudo apt-get install apt-transport-https ca-certificates curl software-properties-common
+        - curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
+        - sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
+        - sudo apt-get -qq update
+        - sudo apt-get install -y qemu-system-x86 docker-ce python-tk
+        - sudo apt-get install -y libsnmp-dev snmp-mibs-downloader
+script:
+        - ./bft -l
+        - ./bft -i
+        - docker build -t bft:node boardfarm/bft-node
+        - yes | ./bft -b qemux86-openwrt -r https://www.dropbox.com/s/ak58icpzta1f0if/openwrt-x86-generic-combined-ext4.vmdk?dl=0 -y -x travisci
+        - grep tests_fail...0, results/test_results.json
+        - cat results/all.log
+after_failure:
+        - yes | BFT_DEBUG=y ./bft -b qemux86-openwrt -r https://www.dropbox.com/s/ak58icpzta1f0if/openwrt-x86-generic-combined-ext4.vmdk?dl=0 -y -x travisci
+        - cat results/all.log

README.md

@@ -23,13 +23,46 @@ Software Setup
 
 If you are a Linux user, and wish to run and/or develop tests, please clone this repository and then install needed libaries:
 ```shell
-apt-get install python-pip curl
+apt-get install python-pip curl python-tk libsnmp-dev snmp-mibs-downloader
 cd openwrt/
 pip install -r requirements.txt
 ```
 
 The file `config.py` is the main configuration. For example, it sets the location of the file that describes the available hardware.
 
+### Compiling Qemu to simulate devices
+
+[Qemu](https://www.qemu.org/) does full system simulation, and boardfarm can use that tool to run tests on simulated devices (e.g. a simulated OpenWrt router). If you want to use qemu, you will want a recent version (3.0 or higher). You may have to compile on your own system, and if so here's how:
+
+```sh
+sudo apt-get update
+sudo apt-get install build-essential zlib1g-dev pkg-config \
+    libglib2.0-dev binutils-dev libboost-all-dev autoconf \
+    libtool libssl-dev libpixman-1-dev libpython-dev python-pip \
+    python-capstone virtualenv wget
+wget https://download.qemu.org/qemu-4.0.0.tar.xz
+tar xvJf qemu-4.0.0.tar.xz
+cd qemu-4.0.0
+./configure
+make
+sudo make install
+```
+
+### Getting Docker for simulated devices
+
+Docker is also useful for creating simulated devices for running tests. To get the latest stable docker and set it up correctly:
+
+```sh
+sudo apt-get update
+sudo apt-get install apt-transport-https ca-certificates curl software-properties-common
+curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
+sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
+sudo apt-get update
+sudo apt-get install -y docker-ce
+# Add your user to the docker group so that you can run docker without sudo
+sudo usermod -aG docker $USER
+```
+
 Hardware Setup
 --------------
 
@@ -230,4 +263,39 @@ The best automated tests share a few qualities:
 
 The goal is to catch bugs in the software being tested. It is an annoying distraction when tests themselves crash. Keep your tests simple so that others can easily figure them out.
 
+Boardfarm overlays
+-----------------
+
+Recently support for having overlays in a separate directory (e.g. a separat
+git repository was added. This allows your own private tests, boards, and
+testsuites, templates that you want to keep separate for whatever reason.
+It's expected that if this is not private you can create a git repo and share
+your layer with others.
+
+The layout of the overlay will look exactly the same as the boardfarm repo:
+
+```
+my_overlay/
+├── devices
+│   ├── my_device.py
+├── html
+│   └── template_results.html
+├── tests
+│   ├── this.py
+│   ├── that.py
+│   └── foobar.py
+└── testsuites.cfg
+```
+
+Tests, devices, and testsuites in your overlay are added to the available
+tests, devices, testsuites. The email templates replace the ones from the main
+boardfarm repo
+
+To specify an over lay you simply need to the space separated overlays to the
+BFT_OVERLAY environment variable:
+
+export BFT_OVERLAY="../boardfarm-foo/ ../boardfarm-bar"
+
+Then after running bft you should have access to your new tests, device types, etc
+
 Good luck and thanks for reading!