Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #13730

DPT repositories checks/"violations" report

From Sandro Tosi <morph@debian.org>
Newsgroups linux.debian.maint.python
Subject DPT repositories checks/"violations" report
Date 2021-11-27 07:10 +0100
Message-ID <DnZ4l-3Xw-1@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Show all headers | View raw


Hello,
while working on something else[1], i noticed how many of the
repositories in the DPT salsa group are in poor shape:

* missing branches
* changes not pushed to salsa
* general misalignment in configuration/setup/organization
* many other small nuances

[1] https://github.com/sandrotosi/debian-python-team-tracker

That makes it hard to make mass work as in [1], so I thought it would
be interesting to have a tool to evaluate the amount of issues our
repos have, and identify such "violations" so that they can be
addressed.

That information is now available at [2].

[2] https://github.com/sandrotosi/dpt-repos-check/blob/main/violations.txt

please take the content with caution, as it's still an early, raw
draft (i spot-checked some of the reported issues, but there could be
bugs/issues) and it contains data that can be outdated (see below re
caching); the fact that the report indicates only 43 repos are without
violations is a bit disarming, but i think the tool tries to err on
the side of verbosity and pedantry, with 2 level of violations (ERROR
and WARNING) to mark which ones are the most important that require
immediate attention vs the nice-to-have ones.

The checks are under-documented, although they should be somehow
self-explanatory. While the current format is just a text file, I plan
on getting it converted to markdown, although I'm still not sure how
to convey that amount of information effectively.

The report is extremely intensive to generate, as it needs to make 10+
API calls to salsa.d.o for each repository, and it gets throttled
quite early in the run (i got away in dev by installing a cache, so
that i could test it without hitting salsa every time, but that makes
some info stale); for that reason, and if we decide is valuable to
generate it periodically, i don't expect to be able to run it more
than once a month (maybe once a week? TBD).

Comments, critics and improvements are welcome.

Thanks,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll thread


Thread

DPT repositories checks/"violations" report Sandro Tosi <morph@debian.org> - 2021-11-27 07:10 +0100
  Re: DPT repositories checks/"violations" report Scott Kitterman <debian@kitterman.com> - 2021-11-27 10:50 +0100
    Re: DPT repositories checks/"violations" report Simon McVittie <smcv@debian.org> - 2021-11-27 12:20 +0100
  Re: DPT repositories checks/"violations" report Stefano Rivera <stefanor@debian.org> - 2021-11-27 15:00 +0100
    Re: DPT repositories checks/"violations" report Louis-Philippe Véronneau <pollo@debian.org> - 2021-11-27 19:20 +0100
    Re: DPT repositories checks/"violations" report Sandro Tosi <morph@debian.org> - 2021-12-10 07:40 +0100
      Re: DPT repositories checks/"violations" report Sandro Tosi <morph@debian.org> - 2021-12-12 07:30 +0100
        Re: DPT repositories checks/"violations" report Louis-Philippe Véronneau <pollo@debian.org> - 2022-01-03 02:00 +0100
          Re: DPT repositories checks/"violations" report Scott Kitterman <debian@kitterman.com> - 2022-01-03 07:40 +0100
            Re: DPT repositories checks/"violations" report Scott Kitterman <debian@kitterman.com> - 2022-01-03 21:20 +0100
            Re: DPT repositories checks/"violations" report Louis-Philippe Véronneau <pollo@debian.org> - 2022-01-03 21:20 +0100

csiph-web