The BULK ACTIONS drop-down in the server list has a number of options related to WPCD:
Apply All Linux Updates
Apply Only Security Updates
There are some things to be aware of when using these actions.
They will only work if you’re an admin. You cannot delegate these to non-admin users.
You are not able to run any bulk options on servers and sites that are DELETE PROTECTED unless you enable the BULK TRASH option in WPCLOUDDEPLOY → SETTINGS → GENERAL → ENABLE BULK TRASH ACTION.
There will likely be a processing delay since items will be handled one at a time. So you might request an operation on 25 servers but they will still be handled one at a time. If your WP-CRON fires every one minute, then it might be 25 minutes or more before all items are processed in the queue.
Actions are applied as a cron process on the server – in other words they are scheduled to be run on the server shortly after we process the item from the queue. This means that you will NOT see any feedback as they are running. It also means that when you look at the PENDING LOGS screen you will likely see your request marked as COMPLETE even though the process has not completed running on the server or might have failed outright. The COMPLETE status on the PENDING LOGS list only means that the process was was sent to the server and scheduled to be run there, not that it has finished running on the server.
To view the results of your request and what the server might have done you should use the LOGS tab to download the appropriate logs and examine them. Or SSH into the servers and view them there.
When running updates, you might want to restart the servers PRIOR to running the updates.
Just because we have provided a convenient mechanism to run these processes across multiple servers does not mean that you don’t have to examine the output of each server to make sure that everything worked as expected!
Finally, please understand that we have provided these options in the BULK ACTIONS dropdown as a convenience. If an option does not seem to be working for a particular server then please try performing the action from inside the individual server detail screen before contacting support.