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


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

h3. Changes from 2017.2.x to 2018.1
TeamCity is tested only under Apache Tomcat 8.5, earlier Tomcat versions are not supported.
Gerrit 2.6 is the minimal version supported by Commit Status Publisher.
The IntelliJ IDEA Project Runner uses JPS 2017.3.4 requiring Java 1.8 as the minimal version.
TeamCity pages are no longer loaded into iframes as a security measure. Plugins providing pages which can be loaded into iframes should make sure that the pages do not perform any modification actions and register the pages via the {{ContentSecurityPolicyFilter.addUnprotectedPath}} API call. See [details|https://youtrack.jetbrains.com/issue/TW-33819].

h4. NuGet feed
* NuGet feed was moved from the server level to the project level: now each project can have its own feed. The "NuGet packages indexer" build feature can be added to build configurations whose artifacts should be indexed.
* Starting from TeamCity 2018.1, .nupkg files will be indexed on the agent side which could slightly increase the time of builds for projects with the NuGet Feed feature and the automatic package indexing enabled or for builds with NuGet Packages Indexer build feature.
* The following NuGet feed-related parameters are deprecated:
** {{teamcity.nuget.feed.auth.server}}
** {{teamcity.nuget.feed.server}}
** {{system.teamcity.nuget.feed.auth.serverRootUrlBased.server}}

- new version
- locators for properties/values with "value:<text>" and without "matchType" dimension (https://youtrack.jetbrains.com/issue/TW-55350)
- filtering builds by agent name when the name contains parentheses symbols, requires additional syntax: agentName:(value:<value>) instead of agentName:(<value>)

h4. Stricter rules for parameter names used in parameter references
Previously TeamCity allowed to use parameters with any characters in their names in parameter references. For instance: %20% was considered a reference to a parameter with name 20. 
Since 2018.1 to be used in a reference, parameter name should satisfy the following requirements:
- the name should not start with numbers
- the name can contain the following characters only: [0-9a-zA-Z._-*]

So, since 2018.1, the %20% is no longer considered as a refernce, and TeamCity will not ask to define parameter with such name anymore. 
But, for compatibility reasons, if there was a parameter with name 20, it's value still will be used during the parameters resolving process.

See also: https://youtrack.jetbrains.com/issue/TW-15538

h4. Other
The bundled ReSharper CLT and dotCover have been updated to version 2018.1.2