Re: Pre-merge CI for Gerrit

2014-12-09 Thread Jan Kundrát
On Tuesday, 2 December 2014 12:05:46 CEST, Jan Kundrát wrote: Right now, the CI runs only for dummy.git (doing nothing) and for trojita.git (doing three separate build & test checks to cover various combinations of ancient and new Qt4, Qt5, clang, gcc and debug and release builds). Doing this f

Re: Pre-merge CI for Gerrit

2014-12-02 Thread Jan Kundrát
On Tuesday, 2 December 2014 12:05:46 CEST, Jan Kundrát wrote: [1] https://gerrit.vesnicky.cesnet.cz/r/167 Sorry for noise, that was a very bad example. A much better one is at https://gerrit.vesnicky.cesnet.cz/r/164 . Because that change has been merged now, the comments are shown collapsed.

Re: Pre-merge CI for Gerrit

2014-12-02 Thread Jan Kundrát
On Tuesday, 2 December 2014 19:46:18 CEST, Albert Astals Cid wrote: Dependencies are the hard part. Any reason you didn't piggy-back on build.kde.org for it? That's right. The reason for not using Jenkins was that the existing KDE's instance was not up to that task without significant changes

Re: Pre-merge CI for Gerrit

2014-12-02 Thread Albert Astals Cid
El Dimarts, 2 de desembre de 2014, a les 12:05:46, Jan Kundrát va escriure: > Hi, > I managed to get a pre-merge continuous integration working with Gerrit. > This means that whenever someone uploads/updates a change to Gerrit, it > gets through a CI run and the result is reported back to Gerrit as

Pre-merge CI for Gerrit

2014-12-02 Thread Jan Kundrát
Hi, I managed to get a pre-merge continuous integration working with Gerrit. This means that whenever someone uploads/updates a change to Gerrit, it gets through a CI run and the result is reported back to Gerrit as an advice -- see e.g. [1] for an example. A KDE developer can still override t