Hi folks,
as some of you might know, I prefer Gerrit over the ReviewBoard for various reasons, including the fact that it presents patches to me as remote git refs, which means that I no longer have to mess with a web interface just to apply a patch locally and to see if it builds. That's why I worked on bringing Gerrit to KDE, and I would like to use Trojita for testing that we got everything right.

Gerrit runs at [1]; you'll need your KDE Identity account for logging in. An overview of Trojita-related bits is at [2]. For a general primer on Gerrit, see [3]. Please note that you will have to upload your SSH pubkeys to Gerrit even though they're already in KDE's LDAP -- there's some missing functionality [4] on the Gerrit's side, unfortunately.

Be careful with what you do in there -- once a change is approved, it will get merged and pushed into git.kde.org. You can use the "dummy" project as a playground.

As usual, it's in quite early testing, and the biggest drawback is that there's no integration with the CI system just yet. I intend to add this -- the end goal is to have a CI system informing us whether the user-supplied patches build and pass tests, and to make sure that the trunk is regression-free.

So, could you please resubmit your pending changes to Gerrit now? See [3] for how to work with this if you have never touched Gerrit before.

With kind regards,
Jan

[1] https://gerrit.vesnicky.cesnet.cz/
[2] https://gerrit.vesnicky.cesnet.cz/r/#/q/project:trojita
[3] http://qt-project.org/wiki/Gerrit_Introduction
[4] http://code.google.com/p/gerrit/issues/detail?id=1124

Reply via email to