TDF Infra Overview. from developers' perspective

Transcription

1 Introduction Christian Lohmaier AKA cloph on irc/elsewhere part of the project since the very beginning (infra side) since a few years employed by TDF initially part-time as infrastructure administrator later fulltime as sysadmin and release engineer cloph@documentfoundation.org

2 TDF Infra Overview from developers' perspective

3 Git repositories (of course) managed by gerrit (more on that later) repository split into parts: core (the essentials if you want to build LibreOffice) help (if you also want to have help offline) translations (if you want LO in a UI language other than enus) translations repo is to be considered read-only as translations are managed (for the most part) in pootle in addition various helper or obsolete repositories

4

5 Git repositories (of course) managed by gerrit (more on that later) repository split into parts: core (the essentials if you want to build LibreOffice) help (if you also want to have help offline) translations (if you want LO in a UI language other than enus) translations repo is to be considered read-only as translations are managed (for the most part) in pootle in addition various helper or obsolete repositories

6 The WIKI (or how to find all the info) contains tons of info and can be overwhelming at first also people have a urge to cover every corner case possible (or rather the specific issue they ran into) not a bad thing per se, but can lead to wall-of-text with the important parts hidden don't try to use search, instead browse via the category entry points more on that later

7

8 The WIKI (or how to find all the info) contains tons of info and can be overwhelming at first also people have a urge to cover every corner case possible (or rather the specific issue they ran into) not a bad thing per se, but can lead to wall-of-text with the important parts hidden don't try to use search, instead browse via the category entry points more on that later

9 OpenGrok sourceindex / searchable website for the code git grep can do serve you wonders, but only if you already have a checkout but links for jumping around are nice to have

10

11 Bugzilla people need to have a way to file bugs QA team does a great job reviewing submissions also using Linux distributions' bugtrackers bots to parse commit message and send notification to bugs with version info

12

13 Bugzilla people need to have a way to file bugs QA team does a great job reviewing submissions also using Linux distributions' bugtrackers bots to parse commit message and send notification to bugs with version info

14 Jenkins and Tinderbox CI systems integrated with gerrit whenever a change is uploaded/updated in gerrit, a build is triggered if the build succeeds, verified status will be set greatly helps to keep master buildable for ~everyone most of the time tinderbox collects results of branches only so only catches problems after the fact not fully covered by jenkins: Release-Build/Baseline configurations android some tinderboxes also provide nightly/daily builds

15

16 Jenkins and Tinderbox CI systems integrated with gerrit whenever a change is uploaded/updated in gerrit, a build is triggered if the build succeeds, verified status will be set greatly helps to keep master buildable for ~everyone most of the time tinderbox collects results of branches only so only catches problems after the fact not fully covered by jenkins: Release-Build/Baseline configurations android some tinderboxes also provide nightly/daily builds

17

18

19 Crashreport collecting service collects data on end-user crashes that then are matched against symbols to demangle more or less Windows-only at the moment

20

21 Other behind-the-scenes stuff crashtesting open, export, readback documents from various sources (bugtrackers for most part, so problematic documents to begin with) goal is to catch regressions early performance stats lcov code coverage reports cppcheck coverity (external service) fuzzer

22

23

24 more external services mailing list(s) provided by freedesktop.org TDF-provided ones don't allow attachments IRC provided by freenode code mirrors github freedekstop launchpad

25 Intermission

26 How to get started (from the project's POV) compile LibreOffice yourself sounds simpler as it sounds depending on OS and hardware used LO is huge, takes hours to compile if you don't already have something in mind to fix, pick one of the EasyHacks deemed to be beginner/entry level tasks that don't require to be familiar with the codebase already submit Licence agreement statement LO is MPL, with history of LGPL

27 Get started publish your change create an account in gerrit webinterface upload a ssh-pubkey to your account setting submit patch for review depending on feedback iterate to adress comments once Jenkins and a reviewer is happy: Profit :-)

28 Hurdles the repository itself Our code repository has a long history especially didn't start off as a git repo has been converted multiple times current git versions are not happy with some of the old commits badly formed author/ address in commit solution: download a git bundle added benefit that it likely is faster as well

29 Hurdles the build requirements linux mostly painless to setup although you might need to spend some time installing packages until configure is happy wiki has samples for a couple of distros that will get you close Windows nowadays also pretty straightforward have to create an account to get older (aka officially known to work) version of Visual Studio 2015 (Community Edition) cygwin can be hard, but wiki provides preselection of necessary packages

30 Hurdles you're using a Mac? not so long ago the easiest system, just install XCode and you were good to go nowadays need to manually install autoconf, automake and similar once again wiki has you covered

31 Is there easier way? lode script is meant to get you going blackbox style

32 Once you come thus far, you are close to the finish line if configure is happy (pay attention to any warnings it might print at the end) all you need to do is wait. And wait some more. Hackfest VM to the rescue prebuilt LibreOffice sourcetree to start digging around while you wait for your machine to compile available for Linux and Windows

33 Hurdles submitting to gerrit wrong ssh key or not using the correct username wrong (anon access only) remote port blocked (boooh!) trying to push directly to active branch git push <what remote> <whatlocally>:<whatonremote> git push origin HEAD:refs/for/master git push logerrit my_branch:refs/for/master %topic=sometopic./logerrit submit master

34 wrong ssh key port blocked (boooh!) trying to push directly to active branch

35 Questions?