(replies inline) On Mon, 26 Jun 2017, James Dumay wrote:
>
> For example, we would like to know what the success rate of the pipeline
> creation process is. We would track events for each stage in the creation
> flow and we can then use a funnel analysis [2] to see what step users drop
> off (e.g. where we have failed). Another usage would be to record what
> browser versions are in use and that data could be used to have a more
> tailored Supported Browser policy for the project.
>
> In addition to improving the user experience, I am in a position at
> CloudBees where I have to decide how our employees time is being spent on
> the Blue Ocean project and having this data would help us spend this time
> more wisely.
>
> The data collected here is intended for development only (e.g. not
> marketing or other nefarious purposes) and is available under the exact
> same terms as the Jenkins Usage Statistics (e.g. email me and I can give
> you access).
>
> As for personally identifiable information, we strictly do not want to
> include this data in any user analytics. To ensure that we can identify a
> users click stream, we have taken a sha256 hash of the instances public key
> and the user ID and reported this back to the store as a key representing
> the user. It would be great to have any security conscious developers
> review this code [4].
>
> If this turns out to be something useful we can look at opening it up to
> more plugins. For this initial spike we are using a service called Keen [5]
> but I would not be against pumping this data our to a service on Jenkins
> project infra (anyone want to write an analytics system?).
Here's me proactively unvolunteering to write an analytics system right to host
in our project infra :P
More seriously though, I don't see any problem as long as you're taking care to
make sure PII isn't being sent to Keen. I've seen a few plugins over the years
do this, and as long as it's respecting the user's Anonymous usage collection
setting, and not being stupid, then it's totally reasonable IMHO.
While I don't think there is any obligation to share what you learn from these
analytics, I'm sure other plugin developers would find your eventual
conclusions useful.
God speed mooncat.
- R. Tyler Croy
------------------------------------------------------
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>
xmpp: [email protected]
% gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
------------------------------------------------------
--
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/20170627154809.6ov3zk7mbpux3xsd%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
