chevah/brink — pull request #6 by adiroiban (2013-06-03 15:12:02+00:00)
Title: [#1401]  Fix sending arguments to test_remote

Problem description
===================

Right now, test_remote fails to send arguments to remote test task.

Why we got into this (5 whys)
=============================

* There was no test when this change was introduced.
* There is no automated way of testing this.

Changes description
===================

I have fixed the test_remote command.

I have update the brink build system to make it a 1st class citizen of the project.

Now lint, test, test_remote, github and pqm command should work.

For testing, I have just merge the demo seesaw project into brink. If everything is ok we can remove the separte seesaw project and only use brink.

There are not to many tests for brink, but hope we will add them in the future, while working on specific improvements.

I have also updated paver.sh bootstrap script to not install brink, when used for brink itself as this is not needed and only generate confusion.

The Windows buildslaves are not working since this branch depends on a change in paver.sh bootstrap script . Windows buildslaves are hardcoded to use the paver.sh script from brink/master and until this branch lands in master, the windows slaves will not work.

After merging the branch, the windows slaves should be functional.

In the future, I plan to create 100% independent build system so that only code from current branch is used during the build system.

How to try and test the changes
===============================

reviewers @alibotean @bnickname

Check that multiple arguments can be passed to test_remote

```
with no wait
paver test_remote brink-ubuntu-1204-x64 -s -v

with wait
paver test_remote brink-ubuntu-1204-x64 -s -v --wait
```