[
https://issues.jboss.org/browse/JBIDE-12432?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-12432:
------------------------------------
JOB_NAME defines which update site was used to pull the resources, as it describes the
update site (jbt aggregate, jbt tests, jbt webtools, jbtis, etc.)
As to the order of the path segments, you agreed to this in November. Why is it NOW a
problem, 5 months later? Besides, it's arbitrary. The whole point is to collect data
which can be parsed later. Having more segments allows you to filter the http log on
different pieces of metadata. Fewer segments == fewer filter options.
Perhaps you want to see ALL the hits for Alpha2? Filter on BUILD_ALIAS
Or you want all the hits for a given feature, regardless of which milestone in which it
was released. Filter on feature ID.
Or if you want all the hits for the whole release, filter on project.version ==
4.1.0-SNAPSHOT.
I would rather capture more than we need in case we need it later, rather than have to
revisit this in 5 months when someone realizes we failed to collect something useful, and
we've lost 5 months of data.
Investigate enabling p2 download statistics
-------------------------------------------
Key: JBIDE-12432
URL:
https://issues.jboss.org/browse/JBIDE-12432
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: updatesite
Reporter: Max Rydahl Andersen
Assignee: Nick Boldt
Fix For: 4.1.0.Alpha2
Just learned about
http://wiki.eclipse.org/Equinox_p2_download_stats today.
Sounds like OpenShift hosted collector plus some queries to a db could do alot on getting
some better updatesite usage info!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira