-
Notifications
You must be signed in to change notification settings - Fork 803
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
Plugin Install: Bump MC stat on success or fail. #21893
Conversation
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖 The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available. Once your PR is ready for review, check one last time that all required checks (other than "Required review") appearing at the bottom of this PR are passing or skipped. Jetpack plugin:
|
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.
Do we want to add some stats to the install_and_activate_plugin
method as well, to check the situations where the plugin is already installed, but not active?
@jeherve I decided to not track the cases where the plugin is already installed/active. What we're mostly interested in with this stat is determining how many sites error when attempting to install a plugin this way. Using the MC Stats package now though! |
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.
Good for the initial quick-grab of stats. This will help us determine, in a broad way, if sideloading is a relatively stable thing we could investigate further for more use.
* master: (22 commits) Update storybook monorepo to v6.4.0 (#21897) Refresh the site's modules and settings after successful product activation (#21886) Plugin Install: Bump MC stat on success or fail. (#21893) Nav Unification: Use correct user capability for the Inbox menu item (#21882) Jetpack: Extend disconnection dialog component to handle multiple steps and accept more props (#21048) Disable CSSTidy property shorthand optimization in the editor or headstart (#21891) Connection UI: Update Composer instructions in README.md (#21890) Partner Compatibility: Adding a unique connection screen for customers who receive a coupon from a Jetpack partner (#21813) Search package: move search dashboard to package - the base (#21865) JITM: wrap CTA below text on small viewports (#21688) Licensing JS Package – fix icon positioning and width (#21878) JITM: new JS and CSS builder (#21874) Support site_intent for `/me/sites` endpoint (#21880) Don't render Critical CSS while generating CritCSS. (#21879) ConnectScreen: make button full width on small screens (#21683) Improve the copy of the license activation banner (#21876) Rename Webpack-built files back from `.min.js` and remove hashes (#21748) Search: Migrate more helper classes to package (#21751) Search: migrate/add search rest API (#21584) Add initial state to the connection package (#21864) ...
Follow-up of the feedback in #21719 (comment)
Changes proposed in this Pull Request:
This bumps an MC stat when Jetpack tries to install a plugin. This install is used in the JITM sideloading functionality. I've only added stats to install as it's most likely to fail (vs activating). We're interested to see how many sites have trouble "sideloading" plugins through this API, particularly as #21719 and #21719 are merged and will likely get activated from wpcom soon after this release.
Stat group:
jetpack-install-plugin
Stat name:
fail-$slug
||success-$slug
Jetpack product discussion
Related discussions
p1HpG7-dzq-p2
#21719 (comment)
p1HpG7-dHF-p2
Does this pull request change what data or activity we track or use?
Yes, but it's non-identifying data. Just an incremental stat count.
Testing instructions:
You should be able to test this with our existing JITMs for WC Services and CreativeMail.