> On 12. Sep 2018, at 06:58, Baptiste Mathus <[email protected]> wrote:
>
> * How does this relate to JENKINS-32485? I seem to understand it could well
> cover it, apart from the required end date?
Basically that, and JENKINS-32485 suffers from tying itself, at least in the
description, to the terrible usage statistics mechanism which doesn't really
have the capacity for extensibility.
> * "Time period (start and end date) during which data collection is enabled
> on the client (end date is mandatory)"
>
> Does this mean plugins will add an extension point for the new Telemetry
> class, and at some point, after the end date, that code will be dead code
> (that will aggressively be removed from core I suppose)?
Yes.
> Do/should we define a max date? If implem says it ends in 2099, I suppose
> it's well like they didn't put any end date? :)
Something we'd need to handle via project policy. The idea is to gather
information for a specific purpose, not "to have it". So any collection defined
to run for longer than a few months will need to be looked at closely. Since
the Jenkins infra team controls access to the collected data (and which data
even gets stored), it should not be a problem in practice.
On top of that it should be noted that some plugins implement their own stats
collection systems, some even ignoring the opt out for usage statistics for
that. So it's not like this will somehow result in a new problem.
--
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/0BF9E52F-EE0F-46CC-B8B1-E0891F20A343%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
