Icon

You are viewing the documentation of TeamCity 2018.x, which is not the most recently released version of TeamCity.
View this page in the latest documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.

 

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • disable Email, Jabber (in the "Administration > Notifier" sections) and possibly also custom notifiers or change their settings to prevent the new server from sending out notifications;
  • disable email verification (in the  "Administration > Authentication" section);
  • be sure not to run any builds which change (e.g. deploy to) production environments. This also typically includes Maven builds deploying to non-local repositories. You can prevent any builds from starting by pausing the build queue;
  • disable cloud integration (so that it does not interfere with the main server);
  • disable external artifact storage (as otherwise running/deleting builds and server cleanup will affect the storage which might be used by the production server);
  • disable Git registry cleanup (or just disable cleanup on the server);
  • disable Commit Status Publishing;
  • disable any plugins which push data into other non-copied systems based on the TeamCity events (like commit status publishing);

    hidden-data
    https://youtrack.jetbrains.com/issue/TW-47362
    

  • disable

    cloud integration (so that it does not interfere with the main server);

    disable functionality to store project settings in VCS: set teamcity.versionedSettings.enabled=false internal property;

    Wiki Markup
    {hidden-data}related issue: [https://youtrack.jetbrains.com/issue/TW-38304]{hidden-data}

  • consider significantly increasing VCS checking for changes interval (server-wide default and overridden in the VCS roots) or changing settings of the VCS roots to prevent them from contacting production servers. Since TeamCity 10.0.3, see also TW-47324.

...