Another good reason to use Gerrit: Jenkins is at your service
If it’s not yet good enough for you that using Gerrit
- is even easier and faster than using zebrapig (you just push your change and you’re done! And if you use git review it’s getting even easier.),
- the review turn-around times are often better when using Gerrit than zebrapig,
- discussing patches can be done both when you’re on IRC and on Gerrit,
then here’s another good reason to use it: I’ve set up Jenkins for all repositories on Gerrit to build every change in a chroot (including sydbox-1, pinktrace-1 and docs).
For now, all reports only go to me (and anyone else who wants to get an email with the result included) and Jenkins will not report back to Gerrit because the setup is quite fragile yet and I want to be sure it works properly before making it do more.
No idea how to use Gerrit? Just read my earlier posts Gerrit Code Review for Exherbo and Gerrit for Core-Devs. Of course, you can ask me, too. 🙂
| I am and have been working on quite a few F/OSS projects: |
