[JBoss JIRA] (JBIDE-20355) oc location preferences: location is not validated, no help is provided
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20355?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20355:
--------------------------------
Labels: help_wanted openshift_v3 port_forwarding_wizard (was: openshift_v3 port_forwarding_wizard)
> oc location preferences: location is not validated, no help is provided
> -----------------------------------------------------------------------
>
> Key: JBIDE-20355
> URL: https://issues.jboss.org/browse/JBIDE-20355
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Andre Dietisheim
> Labels: help_wanted, openshift_v3, port_forwarding_wizard
> Fix For: 4.3.0.CR1
>
> Attachments: oc-binary-path-not-validated.png
>
>
> # EXEC: go to OpenShift v3 preferences (Window->Preferences->OpenShift v3)
> # EXEC: hit "Browse" and choose any file (ex. /tmp/test.txt)
> Result:
> The preferences wont validate your choice. Whatever you pick is used.
> !oc-binary-path-not-validated.png!
> There also is no explanation to what this "oc binary" is. A dummy user would have no idea what this is all about
> Expected:
> The preferences should do basic tests like
> * is it executable?
> * is it an "oc" binary
> ...and add some explanations on what "oc binary" is and how to obtain it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 12 months
[JBoss JIRA] (JBIDE-20167) Openshift Tooling Usage Tracking
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20167?page=com.atlassian.jira.plugi... ]
Alexey Kazakov edited comment on JBIDE-20167 at 8/6/15 10:15 AM:
-----------------------------------------------------------------
Reopened to clarify.
I see that you use a value of events to track failures=0 and success=1. But when you are *counting* events using UsageReporter.getInstance().countEvent() we send the only one event during 24 hours. This event which we actually send will have value = sum of all values of events you have counted.
So if you count five events (two success, three failures, sum of values = 1+1+0+0+0) then we will send one event with value = 2. It's impossible to track success/failures using this approach. You should use values of counted events only for tracking the number of real user events. Not for something else.
You have to *track* events instead of counting them (it means you will send an event immediately with value=0 or 1) so you will have the number of events=number of wizard launches and value of these events will show the % of success/failure.
was (Author: akazakov):
Reopened to clarify.
I see that you use a value of events to track failures=0 and success=1. But when you are *counting* events using UsageReporter.getInstance().countEvent() we send the only one event during 24 hours. This event which we actually send will have value = sum of all values of events you have counted.
So if you count five events (two success, free failures, sum of values = 1+1+0+0+0) then we will send one event with value = 2. It's impossible to track success/failures using this approach. You should use values of counted events only for tracking the number of real user events. Not for something else.
You have to *track* events instead of counting them (it means you will send an event immediately with value=0 or 1) so you will have the number of events=number of wizard launches and value of these events will show the % of success/failure.
> Openshift Tooling Usage Tracking
> --------------------------------
>
> Key: JBIDE-20167
> URL: https://issues.jboss.org/browse/JBIDE-20167
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Burr Sutter
> Assignee: Andre Dietisheim
> Labels: usage
> Fix For: 4.3.0.CR1
>
> Attachments: import_app_v2.png
>
>
> Embed usage tracking logic in the Openshift v3 tooling - allowing us to know how many individuals are using those tools.
> Usage API docs are here: https://github.com/jbosstools/jbosstools-devdoc/blob/master/api/usage/usa...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 12 months