Allow external tests in the CI system

In order for QNX to become a Tier 1 Qt platform it would be extremely valuable for QNX to be included in the CI system.

As discussed on the ML:

http://lists.qt-project.org/pipermail/development/2012-June/004339.html

a proposed solution is to allow external nodes to be told when and what to build and be allowed to feed-back results to the Qt Project CI system.

RIM and KDAB are willing to help achieve this goal as ultimately this will save in man-power and resources needed to verify a Qt release candidate on the QNX platforms.

So how to move this forward? Right now, KDAB has a small Jenkins installation building qtbase, qtxmlpatterns, qtjsbackend and qtdeclarative for a single QNX target configuration.

RIM is in the process of setting up a more complete set of configurations on a fresh Jenkins installation.

I would suggest that we initially work towards a build-only test node that can be incorporated into the CI system. Once that is working we can look at extending it to also run the suite of unit tests on one or more devices.

I do not know how the internal Pulse CI system is put together. Rohan can you propose something for the IPC mechanism that would work for you guys please?