Introduce command scheduler and runner

.travis.yml

@@ -7,33 +7,32 @@ notifications:
     on_success: never
     on_failure: change
 
-branches:
-  only:
-    - master
-
 cache:
   directories:
     - vendor
     - $HOME/.composer/cache
 
 matrix:
   include:
+    # PHPUnit
+    - php: 7.2
+      env: WP_VERSION=latest
+    - php: 7.2
+      env: WP_VERSION=trunk
     - php: 7.1
       env: WP_VERSION=latest
+    - php: 7.1
+      env: WP_VERSION=trunk
     - php: 7.0
       env: WP_VERSION=latest
-    - php: 5.6
-      env: WP_VERSION=4.4
-    - php: 5.6
-      env: WP_VERSION=latest
-    - php: 5.6
+    - php: 7.0
       env: WP_VERSION=trunk
-    - php: 5.6
+    # PHPCS
+    - php: 7.1
       env: WP_TRAVISCI=phpcs
-    - php: 5.3
-      env: WP_VERSION=latest
 
 before_script:
+  - phpenv config-rm xdebug.ini
   - export PATH="$HOME/.composer/vendor/bin:$PATH"
   - |
     if [[ ! -z "$WP_VERSION" ]] ; then

Gruntfile.js

@@ -9,7 +9,7 @@ module.exports = function( grunt ) {
 
 		addtextdomain: {
 			options: {
-				textdomain: 'wp-cli-via-cron-control',
+				textdomain: 'wp-cli-cron-control-offload',
 			},
 			update_all_domains: {
 				options: {
@@ -31,8 +31,8 @@ module.exports = function( grunt ) {
 			target: {
 				options: {
 					domainPath: '/languages',
-					mainFile: 'wp-cli-via-cron-control.php',
-					potFilename: 'wp-cli-via-cron-control.pot',
+					mainFile: 'wp-cli-cron-control-offload.php',
+					potFilename: 'wp-cli-cron-control-offload.pot',
 					potHeaders: {
 						poedit: true,
 						'x-poedit-keywordslist': true

README.md

@@ -0,0 +1,77 @@
+# WP-CLI Cron Control Offload #
+**Contributors:** ethitter, automattic  
+**Tags:** wp-cli, cli, cron, cron control  
+**Requires at least:** 4.8.1  
+**Tested up to:** 4.9  
+**Requires PHP:** 7.0  
+**Stable tag:** 0.1.0  
+**License:** GPLv2 or later  
+**License URI:** http://www.gnu.org/licenses/gpl-2.0.html  
+
+Schedule WP-CLI tasks to run via Cron Control
+
+## Description ##
+
+Offload WP-CLI requests to cron, to be executed via (Cron Control)[https://github.com/Automattic/Cron-Control] and its CLI runner.
+
+Provides a WP-CLI command to schedule these events. A UI is under consideration.
+
+## Installation ##
+
+1. Upload the `wp-cli-cron-control-offload` directry to the `/wp-content/plugins/` directory
+1. Activate the plugin through the 'Plugins' menu in WordPress
+
+## Frequently Asked Questions ##
+
+### Where is command output captured? ###
+
+The actions `wp_cli_cron_control_offload_run_success` and `wp_cli_cron_control_offload_run_error` are fired, allowing you to capture command output as your environment allows.
+
+### Can this be used with commands that manipulate files? ###
+
+This depends on how the commands are written, and the environment that hosts Cron Control's runner. The plugin makes no special accommodations to handle files required by or produced by commands.
+
+### Why is PHP 7 required? ###
+
+To support arrays in constants set using `define()`, PHP 7 is required. These are used to set whitelists and blacklists, though filters are also provided; see below.
+
+### Does this support custom WP-CLI commands? ###
+
+Yes. By default, no restrictions are placed on what commands are supported, as those restrictions depend on the environment where this plugin is used. That said, see the following sections regarding support for whitelists and blacklists.
+
+### Can I dynamically block commands? ###
+
+Yes, using the `wp_cli_cron_control_offload_is_command_allowed` filter. Note that the blacklist described below takes precedence over this filter (the filter is ignored). Additionally, if a whitelist is provided, the filter uses it as the default.
+
+### Can commands be blocked or blacklisted? ###
+
+Yes, using either the `WP_CLI_CRON_CONTROL_OFFLOAD_COMMAND_BLACKLIST` constant or the `wp_cli_cron_control_offload_command_blacklist` filter. If defined, the constant takes precedence and the filter is only able to supplement the constant's blacklist.
+
+Regardless of whether the constant or filter is used, either should provide an array of top-level commands to permit:
+
+```
+array(
+	'cli',
+	'core',
+	'eval',
+	'eval-file',
+)
+```
+
+### Can commands be restricted or whitelisted? ###
+
+Yes, using either the `WP_CLI_CRON_CONTROL_OFFLOAD_COMMAND_WHITELIST` constant or the `wp_cli_cron_control_offload_command_whitelist` filter. If defined, the constant takes precedence and the filter is only able to supplement the constant's whitelist.
+
+Regardless of whether the constant or filter is used, either should provide an array of top-level commands to block:
+
+```
+array(
+	'post',
+	'site',
+)
+```
+
+## Changelog ##
+
+### 0.1.0 ###
+* Initial release

includes/class-command.php

@@ -0,0 +1,48 @@
+<?php
+/**
+ * Class Command
+ *
+ * @package WP_CLI_Cron_Control_Offload
+ */
+
+namespace Automattic\WP\WP_CLI_Cron_Control_Offload;
+
+if ( ! defined( 'WP_CLI' ) || ! \WP_CLI ) {
+	return;
+}
+
+use WP_CLI;
+use WP_CLI_Command;
+
+/**
+ * Offload WP-CLI commands to cron
+ */
+class Command extends WP_CLI_Command {
+	/**
+	 * Create an event to run a given WP-CLI command
+	 *
+	 * @subcommand create
+	 * @synopsis --command=<command> [--timestamp=<timestamp>]
+	 * @param array $args Array of positional arguments.
+	 * @param array $assoc_args Array of flags.
+	 */
+	public function create( $args, $assoc_args ) {
+		$command = WP_CLI\Utils\get_flag_value( $assoc_args, 'command', '' );
+
+		$timestamp = WP_CLI\Utils\get_flag_value( $assoc_args, 'timestamp', null );
+		if ( is_numeric( $timestamp ) ) {
+			$timestamp = absint( $timestamp );
+		}
+
+		$scheduled = schedule_cli_command( $command, $timestamp );
+
+		if ( is_wp_error( $scheduled ) ) {
+			WP_CLI::error( $scheduled->get_error_message() );
+		}
+
+		/* translators: 1: Human time difference, 2. Timestamp in UTC  */
+		WP_CLI::success( sprintf( __( 'Command scheduled for %1$s from now (%2$s)', 'wp-cli-cron-control-offload' ), human_time_diff( $scheduled ), date( 'Y-m-d H:i:s T', $scheduled ) ) );
+	}
+}
+
+WP_CLI::add_command( CLI_NAMESPACE, __NAMESPACE__ . '\Command' );