Development/Gerrit: Difference between revisions

From KDE TechBase
Line 12: Line 12:
** sysadmin's tickets?
** sysadmin's tickets?
*** gerrit admins have to be able to read these
*** gerrit admins have to be able to read these
** anything which needs hard-core stuff like recreating the whole VM: a sysadmin should file a ticket at [email protected]
** anything which needs hard-core stuff like recreating the whole VM: a sysadmin should file a ticket at [mailto:[email protected] CESNET's XIFI support].
* give access to further admins
* give access to further admins
** frederik gladhorn?
** frederik gladhorn?
** tosky?
** tosky?
** ossi?
** ossi?
** Who else? Register at Gerrit, send a mail to [email protected] and I'll make it happen.
** Who else? Register at Gerrit, send a mail to [mailto:[email protected] CESNET's XIFI support] and I'll make it happen.
* Implement the CI
* Implement the CI
** Jenkins, its job builder, zuul,...
** Jenkins, its job builder, zuul,...
** Tool idea: run krazy over submitted patches before committing and inform committer about possible changes
** Tool idea: run krazy over submitted patches before committing and inform committer about possible changes

Revision as of 14:40, 7 September 2014

Gerrit runs at [1], use your KDE Identity to login in and don't forget to upload your SSH keys (bugreport).


BoF at Akademy

Someone suggested to use Frameworks Meeting (Room 1 - September 9th, afternoon).

Also the PIM one (Room 4 - September 9th, morning)

TODO list

  • Documentation: Write a howto for users/developers
  • Define how to get support
    • sysadmin's tickets?
      • gerrit admins have to be able to read these
    • anything which needs hard-core stuff like recreating the whole VM: a sysadmin should file a ticket at CESNET's XIFI support.
  • give access to further admins
    • frederik gladhorn?
    • tosky?
    • ossi?
    • Who else? Register at Gerrit, send a mail to CESNET's XIFI support and I'll make it happen.
  • Implement the CI
    • Jenkins, its job builder, zuul,...
    • Tool idea: run krazy over submitted patches before committing and inform committer about possible changes