Unable to render embedded object: File (TeamCity48.png) not found.

TeamCity 2018.x Documentation

Documentation for Previous Versions

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.

hidden-data
=====================================================================
=====================================================================

h2. Changes from 2018.1.x to 2018.2.x

 
h3. Bundled Tools Updates
 
- TeamCity now uses HSQL 2.4.1 as the default internal database.
- The bundled .NET Tools (dotCover and ReSharper CLT) have been upgraded to the latest released version, 2018.1.4
- Since TeamCity 2018.2 OpenJDK is included in the Windows .exe TeamCity distribution (before 2018.2 Oracle Java was bundled with TeamCity Windows distribution). 





 

Changes from 2018.1.x to 2018.2

...

Known issues

...

Changes from 2018.1.3 to 2018.1.4

Known issues

  • Builds which are running while the server upgrades to 2018.1.4 can get their build log and status truncated, not duly reporting build failure. The build log gets warning with "__tc_longResponseMarker" text (details). It is recommended to wait till there are not running builds when upgrading to this version.

Misc

Support for Microsoft Internet Explorer 10 is discontinued in TeamCity 2018.1.4.

...

The latest JaCoCo version (0.8.2) has been added to TeamCity.

Known issues

If you use JaCoCo coverage and you decide to downgrade from TeamCity 2018.1.3+ to TeamCity versions 2018.1 - 2018.1.2,  you may experience issues requiring manual fixes to make the affected configurations work again.

Changes from 2018.1.1 to 2018.1.2

Known issues

If you are using tcWebHooks third-party TeamCity plugin, update it to the latest version before upgrading (details).

hidden-data
(this was a bug existing since version 9.1, so seems like we do not need to announce it's fixing in 2018.1.2 here - https://youtrack.jetbrains.com/issue/TW-42962)
h3. Agent configuration on upgrade
If you choose to perform upgrade of a TeamCity agent running under Windows using TeamCity Windows agent or server installer and the previous agent version is 9.1+ (regularly, agent upgrades automatically and you do not need to run the installer manually), in order not to lose agent settings stored in <TeamCity Agent Home>\config\buildAgent.properties, backup the file before running the installer and restore the file from the backup after the installation procedure.
 

...

Changes from 2018.1 to 2018.1.1

Known issues

If you're upgrading from 2018.1 to 2018.1.1 and you want to see the NuGet packages missing due to issues TW-55703 and TW-55833, do the following:

...

Changes from 2017.2.x to 2018.1

Known issues

While publishing NuGet packages into the TeamCity NuGet feed in multiple build steps, only the packages published by the first build step will be visible. See TW-55703 for details. If you experience problems with download of NuGet packages published within archives see TW-55833.

...

Changes from 2017.1.3 to 2017.1.4

Known issues

TFS Personal support lists all build configurations for TFVC VCS root. See TW-51497 for details.

...

Changes from 10.0.x to 2017.1

Known issues

Editing cloud profile cancels all builds on profile agents. See TW-49616 for details.

...

Changes from 9.1.1 to 9.1.2

Known issues

The Command line runner can fail to execute a custom script if it has a non-default hashbang specified at the beginning of the script: TW-42498

...