Giters

jenkins-infra / plugin-health-scoring

This project aims to introduce a metric system to calculate the health score of each plugin within the Jenkins ecosystem and reflect the final scores on the Plugin Site for the plugin maintainers and users.

Home Page:https://plugin-health.jenkins.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Compose scoring components description

alecharp opened this issue · comments

commented

The current implementation of a scoring components description limits the composition of probe results.
We will need in the future to be able to express composition like a boolean expression to say "To get this many points, the plugin must have both this probe result valid and this other one".

The current PluginMaintenanceScoring implementation is doing so by having negative points to the secondary requirement, matching the points of the first one. See

plugin-health-scoring/core/src/main/java/io/jenkins/pluginhealth/scoring/scores/PluginMaintenanceScoring.java

Lines 57 to 58 in d2d5497

DependabotProbe.KEY, .15f,
DependabotPullRequestProbe.KEY, -.15f,
.

However, this won't be sufficient when we have to work on RenovateProbe (in #254) for example.

Requirement

Current, we need to be able to express:

  • a direct requirement (probe's key)
  • a and expression between two direct requirement