# run: gobby infinote://gobby.debian.org/debconf17/bof/qa Introduction * Many QA-related sessions at DebConf let's maintain jenkins.debian.org as a team OpenQA - the integration testing framework for fully tested daily releases Patterns for Testing Debian Packages using autopkgtest results for unstable to testing migration Scaling piuparts.debian.org to multiple architectures ci/autopkgtest BoF Reproducible builds: Status update (and more) * QA work seems to go into many directions, but with little "team-like" interactions * Goal of this session: ** Discuss what we are doing (and refresh the 'https://wiki.debian.org/qa.debian.org/activities' wiki page) ** Think about what could be done/improved What's the QA "team" doing? =========================== * Maintain infrastructure to detect problems; report issues ** lintian + lintian.d.o ** piuparts + piuparts.d.o ** ci.debian.net ** jenkins.debian.net / reproducible builds infra ** archive rebuilds * Maintain infrastructure to expose information to maintainers and teams ** tracker.d.o ** packages.qa.d.o ** Debian developer's package overview ** Ultimate Debian Database * MIA Team * New stuff since last year: ** piuparts used for gating to testing ** ci.d.n too at some point? ** archive rebuilds on a regular basis again Discussion items / Stuff we need to do ====================================== Infra: qa.debian.org and the 'qa' SVN repo ------------------------------------------ * Many services glued together, many unmaintained * Kill qa.debian.org and the "qa" SVN repo, move useful services to separate VMs? ** Alternative would be to upgrade it to stretch (and discuss this again in two years) * Get rid of the PTS? blockers? Diffstat of 'qa' since DC16: $ svn diff -r3531 |diffstat bug-summaries/wml/details.pwml | 4 cgi-bin/ddpo | 18 cgi-bin/fakeupstream.cgi | 160 +++++-- cgi-bin/popcon-png | 22 cgi-bin/vcswatch | 13 cgi-bin/watch | 2 contrib/README | 2 data/RELEASES | 9 data/bls/descriptions/I-hardening-wrapper-used.description | 2 data/bls/descriptions/I-invalid-cmake-used.description | 2 data/bls/descriptions/I-no-compiler-commands.description | 2 data/bls/descriptions/W-compiler-flags-hidden.description | 2 data/bls/descriptions/W-dpkg-buildflags-missing.description | 2 data/bls/genhtml.py | 13 data/cronjobs/bls | 4 data/cronjobs/crontab.head | 1 data/cronjobs/ddpo.dm | 2 data/cronjobs/ddpo.watch | 12 data/cronjobs/dose-job | 1 data/ddpo/extract_archive.pl | 4 data/ddpo/extract_incoming.pl | 95 +--- data/ddpo/extract_reproducible.pl | 7 data/ddpo/extract_watch.pl | 40 - data/debcheck/debcheck | 12 data/ftp/calculate-override-disparities | 2 data/ftp/extract-section-priority | 2 data/vcswatch/vcswatch | 19 data/vcswatch/vcswatch.sql | 3 data/wnpp/maintainers-needed.pl | 2 dose/bts.py | 53 +- dose/conf.py | 24 - dose/query-bts.py | 36 - dose/reports.py | 118 ++--- dose/universes.py | 56 +- etc/apache.conf | 1 home/.ssh/authorized_keys | 13 mail/aliases | 11 mia/README | 3 mia/merge-records | 6 mia/mia-save | 20 mia/mutt-orphan | 11 mia/remove-uploader | 11 mia/status.py | 15 pts/bin/forward-tracker-debian-org | 4 pts/mail/.forward-_auto | 1 pts/mail/.forward-_control | 2 pts/mail/.forward-_news | 1 pts/mail/.forward-_uploads | 1 pts/mail/.forward-default | 1 pts/www/bin/config.py | 2 pts/www/bin/excuses_to_xml.py | 4 pts/www/bin/generate_html.sh | 1 pts/www/bin/other_to_xml.py | 49 +- pts/www/bin/tagged_bugs.py | 2 pts/www/bin/update_incoming.sh | 87 ++- pts/www/cgi-bin/soap-alpha.cgi | 2 pts/www/web/common/ubuntu.png | 1 pts/www/xsl/common-params-vars.xsl | 2 pts/www/xsl/pts-issues.xsl | 10 pts/www/xsl/pts.xsl | 274 +++++++----- wml/common-html.php | 12 wml/debcheck.wml | 16 wml/developer.css | 3 wml/developer.wml | 55 +- wml/excuses.wml | 11 wml/howto.wml | 2 wml/index.wml | 2 wml/vcswatch-template.wml | 25 - wml/watch/sf.wml | 23 - Infra: common scheduler for QA checks? -------------------------------------- - ci.d.n uses rabbitmq + systemd timers - duck.d.n uses daily cron - reproducible builds uses jenkins - fedmsg - dead? - mole - dead? Tools: common tool to manage mass bug filings, based on the one used for archive rebuilds? ------------------------------------------------------------------------------------------ Checks: - packages that fail to build twice in a row (dpkg-buildpackage; dpkg-buildpackage) + packages that fail to build reproducibly twice in a row => discussion on -policy@? - packages that fail to build randomly (non-RC :( ) - auto-test rev-[build]-deps before uploads + ruby team tools + ratt + done using the archive rebuilds infra for some important packages MBF: broken packages in unstable -------------------------------- * done: packages not in jessie nor stretch, still not in testing * rolling requirement that packages cannot stay out of testing for 1 or 2 years? (except exceptions) ** (and not updated) action items: ------------- - [lucas] Tools: common tool to manage mass bug filings, based on the one used for archive rebuilds? - [terceiro] common test scheduling - [balint/lucas] simple scripts for rebuilds]