This section provides answers to frequently asked questions about Autopilot.
Yes. Access to Autopilot is account-based and individual sites in that account can turn Autopilot on and off as desired. See Enable Autopilot.
Yes. Configure Autopilot activity digests and notifications in your Personal Workspace settings Notifications tab.
The version(s) of Drush that are supported by Autopilot for sites:
- Up to (not including) Drupal 9: Drush 8
- Drupal 9 with Integrated Composer: Any; Autopilot will use Composer instead of Drush.
- Drupal 9 without Integrated Composer: Drush is not supported. Drupal 9 requires Drush 10 or higher, but Autopilot is not compatible with Drush 10.
Autopilot only supports Drush 8 for all sites up to Drupal 9.
All Drupal 9 sites that use Integrated Composer are compatible with Autopilot.
Autopilot does not use Drush when updating an Integrated Composer site; you can use any Drush version when using Integrated Composer. Refer to the documentation on Drush versions for more information.
You can specify the environments to which Autopilot deploys. See the configuration options.
Autopilot tests updates against a Multidev cloned from the current Dev environment by default. Opt into the Sync Environment feature in the site's Configuration tab to sync your Live environment before Autopilot checks for updates.
No. If you encounter any issues about Multidev limits, contact Support.
Not yet. Currently, Autopilot only supports tests on anonymous access versions of pages. Support for authenticated (logged-in user) page tests is planned for a future release.
Autopilot only checks for changes and updates to modules, themes, and core. You should take time to carefully review and test changes that fall outside of Autopilot's scope, including:
Other backend changes
Yes. Depending on your Account, Autopilot can be set for up to 25 pages on each site. It will check for updates once a week, and can also be run on demand.