Open jtnord opened 3 months ago
Versions appear in the HTML source, my guess is https://github.com/jenkins-infra/infra-statistics/commit/6d7432c852006f3b67a77f7b2aec98d0b94c9043 wasn't comprehensive enough and is missing legal punctuation.
from @daniel-beck in a PM
completely bogus release
We do not filter plugins by known public versions, and show what gets reported.
explains the 221.v8c725fc275c7
that has come from someone then :)
show what gets reported
Noting that we could, like we do for core, we just don't bother at the moment.
Refer to a similar issue that was reported earlier. At that time, it was decided that the results from the fix were worse than the issue:
So allowlisting public releases would be the way to go, no filtering needed later. Do we know enough about where usage-log-decrypter
is run to ensure any such proposal would end up merged and used? Right now the repo state does not look good…
Alternatively, we could check for known public releases in infra-statistics
and filter there.
Any objection if this issue moved to the repository (as there are no actionable for the Jenkins infra team)?
I assume this is related but for all plugins there is no update for the installation count. The last data is from June e.g. for script-security Is there some script not running that updates the stats or is it failing?
Yes, after changes to require VPN Kohsuke's machine can't connect, @dduportal was in contact to resolve last I heard
Absolutely: we are tracking the missing stats in https://github.com/jenkins-infra/helpdesk/issues/4285
Service(s)
stats.jenkins.io
Summary
The statistics for the bouncycastle-api plugin are missing details of the last 4 CD releases.
There is additionally a release present (
221.v8c725fc275c7
) that appears to be bogus.Reproduction steps
221.v8c725fc275c7
versionbouncycastle-api
Note that there are missing releases from the stats data and also release that is bogus.