As per my understanding, for now, the data would only be used by Plugins
Site. If in the future we want to show Plugin's health scores on Plugin
Manager as well then I think every install of Jenkins would need the data.
An object full of values like this:
```
"healthScore": 87,
“healthScoreParameters”: [
{isParentPomLatest : 0.4},
{isJenkinsfilePresent : 0.3},
{checkJenkinsBaseVersion : -0.2},
{checkDeprecatedLayouts : -0.1},
{isSpotbugsEnabled : 0.3},
{isScmUrlUpdated : 0.1},
{isAutomatedDepCheckEnabled : 0.5},
{isUsingPluginBom : 0.4},
{isContributingGuidePresent : 0.2}
.
.
.
]
```
The number of parameters can be expanded very easily and is yet to be
decided specifically, but I think initially there can be around 30~ of them
per plugin. This means 30*2000 = 60000
That's weird, I specifically placed the link of the bookmark within my
proposal which takes us to the exact section which answers your questions.
Link:
https://docs.google.com/document/d/1HTbcWh5C1KrCgEzgqeVEPyfr1H5fH5eTj8KpbWrWsSY/edit#bookmark=id.67e168tnirse
Please let me know what you think about this, thanks!
On Wed, Apr 6, 2022 at 8:58 PM 'Gavin Mogan' via Jenkins Developers <
[email protected]> wrote:
> Does every install for Jenkins need the data? Or would it be only for a
> single view?
>
> How much data is it per plugin? A single number? Or an object full of
> values?
>
> Any data you'd want to add would need to be multiplied by like 2000
> plugins so it gets super expensive super quickly.
>
> I tried reading the proposal but after a couple pages or so I didn't feel
> like skimming any more to try and find this info.
>
> On Wed., Apr. 6, 2022, 5:14 a.m. Dheeraj, <[email protected]>
> wrote:
>
>> Hi everyone,
>>
>> Based on the project idea 'Plugin Health Score' for GSoC '22, I have a
>> small question. Can we deliver each plugin's health score inside the JSON
>> object published by the Update Center?
>>
>> More on this can be found in this proposal
>> <https://docs.google.com/document/d/1HTbcWh5C1KrCgEzgqeVEPyfr1H5fH5eTj8KpbWrWsSY/edit#bookmark=id.67e168tnirse>
>> .
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAET3Cjcwrf_USC1tL-hRM0mDsd9gsa22bR5_rXbpNNj8aoJNGw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAET3Cjcwrf_USC1tL-hRM0mDsd9gsa22bR5_rXbpNNj8aoJNGw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuuzRW%2BSenKMyx-CwhHhyme7mfE187m7xQuudA0o%2BUq02Q%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuuzRW%2BSenKMyx-CwhHhyme7mfE187m7xQuudA0o%2BUq02Q%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CAET3CjefDseaRAbGzAmgDRjPguHfi89p0Wu0nDMQ%3Dsa%2Bff3VLg%40mail.gmail.com.
