On 07.06.2012 08:35, Rohan McGovern wrote: > Molkentin Daniel (Nokia-MP/Berlin) said: >> >>> It means that the current CI infrastructure is operated by Nokia and >>> can't have build nodes plugged in from outside of Nokia premises. So, >>> if you need to manage your own build nodes, there is currently no way to >>> integrate with the Qt Project CI system. Fixing this is a significant >>> project which I am not aware of anyone currently working on :( >> >> >> How likely/far away is it that we can switch from Pulse to Jenkins for CI? >> Because in that case, we could federate CI builds. >> > > Nobody is working on it, so at the current rate of work, it is > infinitely far away :)
Isn't thinking and discussion about also some kind of work? So work > 0 and 1/work < infinity ;) > >> Given that the actual logic should be shell/perl/python scripts, this should >> be doable, right? >> > > The scripts which have the logic for testing are not at all Pulse > specific and can already be used successfully in Jenkins, or any other > decent CI tool. > > The glue between gerrit and Pulse would have to be rewritten to support > Jenkins, but this is small (and that code is long overdue a complete > rewrite). > > I don't think it matters much which one of these tools is used at that > layer, they're all pretty similar. > _______________________________________________ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
