-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
telemetry: start tracking flags usage #6168
telemetry: start tracking flags usage #6168
Conversation
✅ Deploy Preview for odo-docusaurus-preview canceled.
|
@kadel: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you change the target branch for this PR to release/v3.0.0
instead, to have this in v3 GA? main
already contains a bunch of code refactoring and a few other changes (like #6166) are coming in as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another comment. I saw that we have a few integration tests related to telemetry, checking the values in $ODO_DEBUG_TELEMETRY_FILE
.
It would be great to also update some of those tests that use flags, I think.
Example with cmd_devfile_init_test
: https://github.com/redhat-developer/odo/blob/release/v3.0.0/tests/integration/cmd_devfile_init_test.go#L347-L366
Closing and reopening to (hopefully) trigger the IBM Cloud tests. |
Retriggering the tests by closing and reopening the PR. FYI, @dharmit (as test boss this week ;-)), below are the issues: OpenShift:
Windows (however, because of #6175, I would not have much confidence in Windows tests for this PR):
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rm3l The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@kadel Looks like you have rebased onto |
yeh :-( |
Windows tests failing due to some (temporary?) network issues? cc @feloy (as test boss this week ;-)) Retrying one more time.. |
Kudos, SonarCloud Quality Gate passed! |
/override windows-integration-test/Windows-test |
@feloy: Overrode contexts on behalf of feloy: windows-integration-test/Windows-test In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What type of PR is this:
/kind feature
What does this PR do / why we need it:
Record what flags are used when the odo command is executed.
This will be helpful to get more insights what features are being used.
For example, currently, we can't see how many users user debug mode
odo dev --debug
or--no-watch
feature. With this, we will be able to get more insights if those features are being used.It would be nice to include this in the v3 GA build, so we can start tracking this from the beginning.
PR acceptance criteria:
Unit test
Integration test
Documentation
How to test changes / Special notes to the reviewer: