I'm curious why this test exists and if it was ever useful. It does things like check to see if every Gerrit repository has a defined test (which I'm not sure has ever been the case).
There are also a few assertions that are out of date, like: All Jenkins jobs use DebianJessie label when we have T239981: Delete Jenkins label DebianJessie
We should fixup these tests or ditch the job.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| integration-config-qa: skip email for now | integration/config | master | +0 -14 |
Change 571751 had a related patch set uploaded (by Thcipriani; owner: Thcipriani):
[integration/config@master] integration-config-qa: skip email for now
Change 571751 merged by jenkins-bot:
[integration/config@master] integration-config-qa: skip email for now
Introduced in rCICF7b0213a1756d: Periodic QA job for integration/config.git and then used for various things like rCICF2bac0e28e5f2: QA report for gated extensions and their dependencies
That is intended to show up a dashboard of things that should be fixed in integration/config , for example a Gerrit repository which is not defined in Zuul. So it is merely a never ending task.
The view is https://integration.wikimedia.org/ci/job/integration-config-qa/lastBuild/testReport/
Possibly we can make the job to ignore test errors and only fail if the test system itself had an issue. Then process the test results and published to some place, maybe somewhere at https://doc.wikimedia.org/