Conversation
| md5 hash verified: 179fc8dacbfe3ebc2d00ba57a333c982 | ||
| New version works. Proceeding to replace. | ||
| Success: Updated WP-CLI to 1.4.0. | ||
| $ wp @daniel option get home |
There was a problem hiding this comment.
This was meant as a smoke test...
There was a problem hiding this comment.
A smoke test that only works on your machine :-)
What‘s a good alternative?
There was a problem hiding this comment.
How about:
$ wp cli version
WP-CLI 2.8.1
$wp eval 'echo \WP_CLI\Utils\http_request( "GET", "https://api.wordpress.org/core/version-check/1.6/" )->body;' --skip-wordpress
<PHP serialized string with version numbers>
That would at the very least test whether the update worked and whether regular execution and the integration with Requests works.
Note: The above example that Daniel provided mostly just tested the SSH subsystem. The entire option retrieval logic is executed on whatever version is installed on his server.
Co-authored-by: Daniel Bachhuber <daniel.bachhuber@automattic.com>
| md5 hash verified: 179fc8dacbfe3ebc2d00ba57a333c982 | ||
| New version works. Proceeding to replace. | ||
| Success: Updated WP-CLI to 1.4.0. | ||
| $ wp @daniel option get home |
There was a problem hiding this comment.
How about:
$ wp cli version
WP-CLI 2.8.1
$wp eval 'echo \WP_CLI\Utils\http_request( "GET", "https://api.wordpress.org/core/version-check/1.6/" )->body;' --skip-wordpress
<PHP serialized string with version numbers>
That would at the very least test whether the update worked and whether regular execution and the integration with Requests works.
Note: The above example that Daniel provided mostly just tested the SSH subsystem. The entire option retrieval logic is executed on whatever version is installed on his server.
danielbachhuber
left a comment
There was a problem hiding this comment.
Thanks for improving our docs!
Based on yesterday's experience