Jump to content

Sysadmin/FutureInfrastructure: Difference between revisions

From KDE Community Wiki
Mck182 (talk | contribs)
Oh so the uploading changes via web was already there, I merged it for better readability
Mck182 (talk | contribs)
Add "Ability to merge patch directly from Web UI"
Line 58: Line 58:
| ?
| ?
| ?
| ?
|-
! Ability to merge patch directly from Web UI
| ?
{{GreenCell}} Yes
|-
|-
! CI Integration
! CI Integration

Revision as of 13:35, 23 January 2015

This page aims to give an overview over the infrastructure that KDE relies on. It tries to give an overview in a feature matrix such that we, the community, can make an informed decision about the merits of each contestant.

Feature Phabricator Gerrit
Git Repository Hosting Yes Yes
Git Repository Browsing Diffusion Integration with external viewer (see our instance)
Git Commit Browsing Diffusion Integration with external viewer (see our instance)
Anongit needs custom implementation Built-in replication
Project Tree Structure No No
Pre Commit Review Differential Yes
Fine-grained review (separate labels, +1/+2,...) No Yes
Bypass Reviews Yes Yes
Scratch Repository WIP A simple script for forwarding one API call
Uploading changes via Git No Yes
Uploading changes via Web Yes https://tools.wmflabs.org/gerrit-patch-uploader/
Downloading changes via Git No Yes
Downloading changes via Web ? ?
Ability to merge patch directly from Web UI ? Yes
CI Integration http://www.guywarner.com/2014/06/part-2-integrating-phabricator-and.html or http://www.dctrwatson.com/2013/01/jenkins-and-phabricator/ Native, see KDE gerrit demo
Closing Bugs on Bugzilla existing git hooks Native support via its-bugzilla gerrit plugin
Post Commit Review Audit Commenting on closed reviews
Clustering for scalability No (?) Yes

Please extend the list, and correct anything thats wrong. Please add links wherever appropriate.