[ https://issues.jboss.org/browse/JBIDE-12432?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-12432: --------------------------------------------- looks like p2 itself have issues actually generating the right stats. WTP team seem to have a tool to "massage" generated site to have properties. http://wiki.eclipse.org/WTP/Releng/Tools/addRepoProperties -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12432?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12432: ------------------------------------ OK, so I need to know the URL to use for the tracker. I'm assuming something like https://devstudio.jboss.com/usage/juno/6.0.0.Beta1/ https://devstudio.jboss.com/usage/juno/6.0.0.CR1/ https://devstudio.jboss.com/usage/juno/6.0.0.GA/ ... Also need to know if we want different trackers for JBT vs. JBDS, and if so if you want one on *download.jboss.org* and another on *devstudio.jboss.com*, or if we can put both on the same server. +1 for both on devstudio server because then we can use Google Analytics to look at the hits (or get httpd logs from ONE source instead of two). And I'm assuming you want to track the top feature for every project as well as the com.jboss.jbds* features, eg., org.jboss.tools.jmx.feature,org.jboss.ide.eclipse.archives.feature,org.jboss.ide.eclipse.as.serverAdapter.wtp.feature,org.jboss.ide.eclipse.as.feature,... We could also track plugins if that's better - depends on the goal we're trying to achieve here. Is this just to supplement usage tracker w/ stats for features downloaded vs. those installed & in use? -- Prototype script to add this to an existing repo (needs to be converted to Ant to be embeddable within a pom): http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/p2stats.sh -- 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

[ https://issues.jboss.org/browse/JBIDE-12432?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12432: ------------------------------------ All that the tracker does, afaict, is hit a URL when a jar is downloaded, like a pingback. So we can track those 404'd requests and voom - download stats. I've enabled this script to generate metadata for stat tracking here: http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/build.xml Hate to commit-and-run, but it should work as is and I can verify it tomorrow when we settle on which URLs to use. Currently, it's hard coded to use https://devstudio.jboss.com/usage/juno/4.0.0.Beta1/ but we can parameterize that for JBT vs. JBDS and key in on the specific releases too. -- 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

[ https://issues.jboss.org/browse/JBIDE-12432?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-12432 at 10/5/12 2:00 AM: ------------------------------------------------------------- Running in Jenkins I get this about half the time: {code} [add] INFO: repository rewritten [add] gogo: InterruptedException: sleep interrupted [add] java.lang.InterruptedException: sleep interrupted [add] at java.lang.Thread.sleep(Native Method) [add] at org.apache.felix.gogo.shell.Activator.run(Activator.java:72) [add] at java.lang.Thread.run(Thread.java:662) {code} or {code} [add] gogo: CommandNotFoundException: Command not found: gosh [add] org.apache.felix.gogo.runtime.CommandNotFoundException: Command not found: gosh [add] at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:466) [add] at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:395) [add] at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108) [add] at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183) [add] at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120) [add] at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89) [add] at org.apache.felix.gogo.shell.Activator.run(Activator.java:75) [add] at java.lang.Thread.run(Thread.java:662) {code} and either the repo's updated correctly ... or not. Also, while the site/target/site/artifacts.jar file IS updated (sometimes - maybe NFS write problem?), it appears that the site/target/site_assembly.zip is NOT updated. Need to ensure we're updating that zip w/ the new artifacts.jar. was (Author: nickboldt): Running in Jenkins I get this about half the time: {code} [add] INFO: repository rewritten [add] gogo: InterruptedException: sleep interrupted [add] java.lang.InterruptedException: sleep interrupted [add] at java.lang.Thread.sleep(Native Method) [add] at org.apache.felix.gogo.shell.Activator.run(Activator.java:72) [add] at java.lang.Thread.run(Thread.java:662) {code} or {code} [add] gogo: CommandNotFoundException: Command not found: gosh [add] org.apache.felix.gogo.runtime.CommandNotFoundException: Command not found: gosh [add] at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:466) [add] at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:395) [add] at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108) [add] at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183) [add] at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120) [add] at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89) [add] at org.apache.felix.gogo.shell.Activator.run(Activator.java:75) [add] at java.lang.Thread.run(Thread.java:662) {code} and either the repo's updated correctly ... or not. -- 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

[ https://issues.jboss.org/browse/JBIDE-12432?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12432: ------------------------------------ How do you propose we test this without it being in a trunk build? I wonder if we can build locally and still log the pingback when installing from http://localhost or file://where/it/was/built/ ... As to GA, would it not appear here? https://www.google.com/analytics/web/?hl=en&pli=1#report/content-page... -- 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

[ https://issues.jboss.org/browse/JBIDE-12432?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12432: ------------------------------------ I *could*, this is true, but I've implemented this to work as part of the AGGREGATE site builds, not for each component site. -- 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

[ https://issues.jboss.org/browse/JBIDE-12432?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-12432: ------------------------------- Fix Version/s: 4.0.0.CR1 (was: 4.0.0.Beta1) -- 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

[ https://issues.jboss.org/browse/JBIDE-12432?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-12432: ------------------------------- Fix Version/s: 4.1.0.Alpha1 (was: 4.0.0.CR1) -- 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

[ https://issues.jboss.org/browse/JBIDE-12432?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-12432 at 11/22/12 5:15 PM: -------------------------------------------------------------- Pull request 12 - https://github.com/jbosstools/jbosstools-build-sites/pull/12/files - moves the tracker to download.jboss.org to try it there instead of devstudio.jboss.com; improves the # of data items collected per feature downloaded. Note that tests today indicate that we're tracking DOWNLOADS, not INSTALLS. Should a user decide NOT to install a collection of features after seeing the 'unsigned content' warning, the download hits are already registered to the server. was (Author: nickboldt): Pull request moves the tracker to download.jboss.org to try it there instead of devstudio.jboss.com; improves the # of data items collected per feature downloaded. Note that tests today indicate that we're tracking DOWNLOADS, not INSTALLS. Should a user decide NOT to install a collection of features after seeing the 'unsigned content' warning, the download hits are already registered to the server. -- 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

[ https://issues.jboss.org/browse/JBIDE-12432?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12432: ------------------------------------ Sample hits logged on download.jboss.org - tool is working! {code} a.b.c.d - - [22/Nov/2012:17:07:15 -0500] "HEAD /jbosstools/usage/4.1.0/Alpha1/jbosstools-4.0_trunk.webtools.aggregate/4.1.0.Alpha1-v20121212-0102-B69/org.jboss.ide.eclipse.as.archives.integration.feature HTTP/1.1" 404 - "-" "Jakarta Commons-HttpClient/3.1" a.b.c.d - - [22/Nov/2012:17:07:15 -0500] "HEAD /jbosstools/usage/4.1.0/Alpha1/jbosstools-4.0_trunk.webtools.aggregate/4.1.0.Alpha1-v20121212-0102-B69/org.jboss.ide.eclipse.as.feature HTTP/1.1" 404 - "-" "Jakarta Commons-HttpClient/3.1" a.b.c.d - - [22/Nov/2012:17:07:15 -0500] "HEAD /jbosstools/usage/4.1.0/Alpha1/jbosstools-4.0_trunk.webtools.aggregate/4.1.0.Alpha1-v20121212-0102-B69/org.jboss.ide.eclipse.as.jmx.integration.feature HTTP/1.1" 404 - "-" "Jakarta Commons-HttpClient/3.1" a.b.c.d - - [22/Nov/2012:17:07:16 -0500] "HEAD /jbosstools/usage/4.1.0/Alpha1/jbosstools-4.0_trunk.webtools.aggregate/4.1.0.Alpha1-v20121212-0102-B69/org.jboss.ide.eclipse.as.server.rse.integration.feature HTTP/1.1" 404 - "-" "Jakarta Commons-HttpClient/3.1" a.b.c.d - - [22/Nov/2012:17:07:16 -0500] "HEAD /jbosstools/usage/4.1.0/Alpha1/jbosstools-4.0_trunk.webtools.aggregate/4.1.0.Alpha1-v20121212-0102-B69/org.jboss.ide.eclipse.as.serverAdapter.wtp.feature HTTP/1.1" 404 - "-" "Jakarta Commons-HttpClient/3.1" {code} -- 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

[ https://issues.jboss.org/browse/JBIDE-12432?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12432: ------------------------------------ Yes, URL prefix can be changed easily to add the /installs/ segment, even though technically we're tracking *DOWNLOADS*, not *INSTALLS*. Need details. WHICH features should we track, if not all? WHAT context do you want? WHAT additional info would you like stored? -- 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