There are a few jobs with a few giga bytes of artifacts. The total is ~ 220GB on contint1001. We should reduce it.
```
$ sort -nr jenkins-build-sizes.txt |head -n 10
221978 /srv/jenkins/builds
63193 /srv/jenkins/builds/mediawiki-fresnel-patch-docker
33194 /srv/jenkins/builds/mwcore-codehealth-patch
13786 /srv/jenkins/builds/wmf-quibble-core-vendor-mysql-php72-docker
11116 /srv/jenkins/builds/wmf-quibble-vendor-mysql-php72-docker
10292 /srv/jenkins/builds/mwcore-phpunit-coverage-master
10255 /srv/jenkins/builds/wmf-quibble-selenium-php72-docker
9340 /srv/jenkins/builds/mediawiki-quibble-vendor-mysql-php72-docker
8515 /srv/jenkins/builds/quibble-vendor-mysql-php72-docker
7990 /srv/jenkins/builds/mwcore-codehealth-master-non-voting
```
I had previously added a patch to compress the MediaWiki Junit files after they have been processed by the Jenkins Junit plugin. Possibly we could just delete them instead since Jenkins aggregates them in a single one.
[x] `mwcore-codehealth-patch` runs the SonarQube Scanner with debug logging (`-X`).
[ ] `mediawiki-fresnel-patch-docker` has a performance json trace file for each test. It is an uncompressed file so that users can drag'n drop it to the Chromium performance tab.