On Thursday 07 June 2012 09:41:49 Thiago Macieira wrote: > Do we need to? > > I know the Gerrit control is a script that Sergio wrote one year ago. I > think we need a two-step solution: > > 1) make a command stream that has a "here, start testing this". It can be > something as simple as a public TCP socket that that never receives, but > prints a line with the build ID whenever it's ready to test. If public is a > security concern, we can allow only specific SSH keys. This should be > relatively simple. > > Bonus target is for it to produce a "stop testing, this has already failed" > command. > > 2) modify the above to receive a reply from authorised sources containing a > pass / fail and, maybe, logs. This is much more complex, since it needs to > deal with connections breaking. The CI control script needs to be modified > to accept multiple replies and produce a conclusion.
This seems like a very pragmatic approach to incorporating additional testing into the CI system. It also has the additional benefit that 3rd parties (i.e. RIM) will be able to host the build server and a number of devices for running the built unit tests in-situ. I will file a JIRA task as Rohan suggested so that we can coordinate things there. Thanks, Sean -- Dr Sean Harmer | sean.har...@kdab.com | Senior Software Engineer Klarälvdalens Datakonsult AB, a KDAB Group company Tel. Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322) KDAB - Qt Experts - Platform-independent software solutions _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
