Vagrant Development and Testing

[nand0p]

Vagrant assists with buildbot development and testing.

Ensures master and worker are working as expected from
a configurable buildbot fork and branch, and runs test suite.

[mention-bot]

@nand0p, thanks for your PR! By analyzing the history of the files in this pull request, we identified @ashcrow, @tardyp and @rutsky to be potential reviewers.

[tardyp]

I am not sure how vagrant could be better than a simple virtualenv development environment.
How fast is the development loop with this?

If you really insist on having a fully independent local test environment, there is buildbot_travis runner:

bbtravis run -j4 --docker-image buildbot/metabbotcfg

This will run the officially maintained tests using. It works well, but I don't really use it as he virtualenv setup is much more simple, integrated with editors, etc.

[nand0p]

The advantage of this is it allows you to easily pull and test from a specified buildbot fork/branch. It also automates the process of creating master.cfg for testing, and ensures master comes up correctly and tests worker registers with master successfully. It also eliminates any issues with developing on OSX with virtualenv.

I find this useful, but if this is not deemed appropriate, i will close this PR. Please advise.

[tardyp]

• for testing any fork/branch you just need to push a PR, and our CI infra will run the test suite in 21 different configurations
• We already have automatic e2e master creation in the smokes directory, with protractor driven UI tests
• what is the issue with osx virtualenv? I am writing all my contributions on osx without any issue