Testing Jetpack on VIP Go

VIP Go platform specific

This document is for sites running on VIP Go.

Learn more

Overview #

Automattic tests Jetpack releases against a diverse range of environments and sites, to assess performance with various levels of data and traffic. There is also an automated Jetpack test suite, run on Travis, which you can follow. As the Jetpack code is a significant proportion of your VIP Go site, we recommend you test your particular functionality against betas and release candidates of Jetpack as they become available. In advance of a Jetpack release, the WordPress.com VIP team will post in the Lobby to keep you informed, we’ll post to our @wpvipstatus when Jetpack or WordPress are updated on VIP Go.

This document describes how to switch your VIP Go site(s) and development environment to use the current beta or release candidate version of Jetpack. You may wish to read about VIP Go sites and environments.

↑ Top ↑

Step 1: Add the version of Jetpack to be tested #

Commit the version of Jetpack you wish to test into your VIP Go site GitHub repository, add it as a directory inside the client-mu-plugins directory (only add the directory, do not add an additional file referencing the plugin directly into client-mu-plugins.)

Each beta can be downloaded from the Jetpack page on the WordPress.org plugins repository, scroll to the bottom of the page and under “PREVIOUS VERSIONS” choose the beta you need from the select box dropdown, then click “download. To be certain you bring across all files, delete any previous jetpack directory and add it from the download you just made. If you have any questions, please contact us.

↑ Top ↑

Step 2: Load the “local” version of Jetpack #

By default, VIP Go will load Jetpack from the MU plugins directory. Using the WPCOM_VIP_JETPACK_LOCAL constant, you can instruct VIP Go to load Jetpack from the client-mu-plugins directory.

Note:  the directory has changed, it used to be plugins but is now client-mu-plugins, if you’ve used this technique before you will need to change your method.

define( 'WPCOM_VIP_JETPACK_LOCAL', true );

If you want to avoid testing on your production site, for example during the beta period (you may choose to run the release candidate on your production site):

$disallowed_jetpack_test_envs = array(
    'production',
);
if ( ! in_array( VIP_GO_ENV, $disallowed_jetpack_test_envs, true ) ) {
    define( 'WPCOM_VIP_JETPACK_LOCAL', true );
}

Note that the previous method of testing Jetpack using the VIP_JETPACK_ALT is discontinued, and this constant will have no effect.

Ready to get started?

Drop us a note.

No matter where you are in the planning process, we’re happy to help, and we’re actual humans here on the other side of the form. 👋 We’re here to discuss your challenges and plans, evaluate your existing resources or a potential partner, or even make some initial recommendations. And, of course, we’re here to help any time you’re in the market for some robust WordPress awesomeness.