Laszlo Papp said: > > 1) Build and software testing service > Is there a build and software testing service provided for projects in > the Qt Playground repositories ? I have not seen any mentionings about > that so far. and it is an important question in my case, for instance. > I have been using CDash [1] for projects under the KDE umbrella. It is > possible as long as I use cmake as a build system in my project. I > think such a build and software testing service along with the > publishing of the build results would increase the QA of those > playground projects. I know there are such QA services for "final" > modules. I was just curious if those tools, providing the relevant > services, are available to Qt Playground projects or not. If not, are > there some other options ? It would be really nice if playground > projects could get such an attention. I am not willing to propose it > for all the projects there because I do not know the capacity, but at > least for projects and maintainers there who are interested in this > matter. >
Security is a potential issue for providing the same test resources used for the main Qt modules to be also used against playground modules. These test machines are Internet-connected[1], and arbitrary code can be set up to run on them; lowering the barrier for getting this arbitrary code onto the machines of course increases the security risk. > http://my.cdash.org/ It would be interesting to know for example how Kitware handled this issue for the above, or if it was explicitly decided to accept the risk (which may well be a valid approach, given that the process includes a trusted maintainer signing off on the new playground project). [1] perhaps not forever - I'm describing the way things are and not necessarily the way they should be :) _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
