Added sru.whitelist used to test stable release update kernels.
Set the "only_changes" parameter default value to False in get_script_env()

jobs not requiring a specific user to run has to use a verbatim copy of the environment.
vagrant: fix broken provisioning on existing vm

vagrant would break on failing provisioning command.
Running `ln -sf /vagrant /home/vagrant/checkbox` would fail
if the target was an existing symlink. The --no-deference
allows one to re-run `vagrant provision` multiple times

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
"[r=zkrynicki][bug=][author=zkrynicki] automatic merge by tarmac"
"[r=zkrynicki][bug=][author=sylvain-pineau] Set the "only_changes" parameter default value to False in get_script_env()"
"[r=zkrynicki][bug=][author=roadmr] automatic merge by tarmac"
docs: add a warning to the front page
jobs/miscellanea.txt.in - provide REPOSITORY and SOURCES_LIST environment
variables to the sources_test script (LP: #1149288)
Updated sources-list job to use multiple lists and repositories by brendand
vagrant: fix broken/missing plainbox.egg-info in test-in-vagrant.sh

This elusive bug kept the CI loop broken/offline for a couple of days.
There are several earlier attempts to fix this but they were all mislead
into fixing non-issues.

The root issue is that "plainbox/setup.py test" fails iff:
 * plainbox was 'developed' by running plainbox/setup.py develop earlier
 * plainbox/plainbox.egg-info (directory) was removed

When those two things happen in sequence, setuptools is tripping over
a bug where it does not re-generate egg-info and crashes while trying
to open it.

The workaround is to always rebuild egg-info before touching plainbox
tests or running the executable generated by distribute.

Testing instructions (verified on 12.04):

 1) $ pip install distribute==0.6.35
 2) $ sudo python3 plainbox/setup.py develop
 3) $ rm -rf plainbox/plainbox.egg-info
 4) $ plainbox/setup.py test

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
vagrant: configure apt cache if $VAGRANT_APT_CACHE is set

This setup allows apt-cacher-ng to quickly fuel construction and upgrade
of virtual machines. This is perfect for testing in vanilla conditions
or debugging issues with the test system itself.

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
"[r=roadmr][bug=][author=zkrynicki] automatic merge by tarmac"
New version 0.15.5