Better logging of failures for our issue-bot
Filing this issue in reference to Hans' request:
In several cases, issue-bot (at RFPs) fails to scan a repo without giving any reason – so it's hard to say a) what went wrong and b) how to improve it (so we could eventually tell whether the source scanned has any issues). So I propose to have it give some more details:
- in it's report, at least a short hint like, "found no gradle nor Manifest, skipping"
- in the logs (CI CLI output) more details on what directories it checked/skipped etc.
Specific examples to test with (I'll update this list whenever I find a case not yet (sufficiently) covered):
-
not even a section mentioning the scan: rfp#1042 (closed), rfp#1051 (closed) -
mentioning versionCode/versionName mismatch, but not saying where the mismatch was seen: rfp#1052 (closed), rfp#1046 (closed), rfp#1018 (closed), rfp#1012 (closed) (and more) -
just adding the fdroid-bot and git-url badges without any details at all: rfp#1048 (closed), rfp#1041 (closed), rfp#1032 (closed), rfp#1030 (closed) (many more)
(made this a check-list so items can be marked once covered/fixed)