disabling triggers.

Hi Ron,

You can manually pause the build queue before server start. The queue state is saved in <TC Data Directory>/config/plugin.queue-pauser.xml file. To pause the build queue please change <param name="queue-enabled" value="false" />. Then if needed you can manually delete all builds from the queue.
Triggers description are stored in xml files, not in database. So another option is to create a script that will modify .xml files of all build configurations stored in <TC Data Directory>/config/projects/<ProjectID>/buildTypes. It should find all triggers in

<build-triggers>
      <build-trigger id="vcsTrigger" type="vcsTrigger">
       ...
      </build-trigger>
</build-triggers>

section and add triggers names to this section:

    <disabled-settings>
      <setting-ref ref="vcsTrigger" />
    </disabled-settings>

Hello,

In addition, a delete triggers could be done by script (this is not a disable, but could be ok for a restore check or environment load without impacts on the original target).

In <TC Data Directory> (aka: .BuildServer) directory, execute this shell command line;

for FILE in `find config/projects/*/buildTypes/*.xml`; do sed -i '/<build-triggers>/,/<\/build-triggers>/d' $FILE; done

Best regards

Disable them all even the paused ones

for i in $(curl -u creds:here --header "Accept: application/json" -X GET http://teamcity.url/app/rest/buildTypes/ | jq -r '.buildType[] | .id '); do curl -u credo:here -H "Content-Type: text/plain" -X PUT http://teamcity.url/app/rest/buildTypes/id:${i}/paused -d "true";done