We need to be able to pause the entire server before an upgrade and then resume after the upgrade.

We can't do an upgrade until the build queue is empty.
We have many servers to upgrade.
Each server has many configurations.
We are finding it very challenging to prevent jobs from running.

On each of our servers we have configurations and promotions in many different states
* Some configurations are disabled
* Some configurations are enabled
* Some configurations with schedules are paused
* Some configurations with schedules are not paused
* Some configurations have promotions that trigger other configurations. The promotions are enabled.
* Some configurations have promotions that trigger other configurations. The promotions are disabled.
* There are other systems that submit builds via the REST API

It's impossible to use the UI to go through every configuration, promotion, etc and disable them.

Even if we could, it's very difficult to remember which ones were enabled/disabled after the upgrade.

We could try to document it as we go but there is still the possibility for mistakes.

To make matters worse, we have to upgrade about many QuickBuild servers. So for us "administrators" the problem just gets worse as more teams in the organization adopt QuickBuild and we setup more servers that need to be upgraded.

We need to be able to completely automate the upgrade process.

In order to automate everything we need a way to pause anything that could result in something running in the build queue.

Then after the upgrade is complete we need to be able to restore all settings (configurations, promotions, scheduled) to the state they were in when we paused them.

We need a REST API and/or a pause(.sh|.bat) resume(.sh|.bat) that will allow us to prevent new jobs showing up in the build queue.