Changes from 6.5.5 to 6.5.6
No noteworthy changes
Changes from 6.5.4 to 6.5.5
(Known issue infex in 6.5.6) .NET Duplicates finder may stop working, the patch is available, please see this comment: http://youtrack.jetbrains.net/issue/TW-18784#comment=27-261174
Changes from 6.5.3 to 6.5.4
No noteworthy changes
Changes from 6.5.2 to 6.5.3
No noteworthy changes
Changes from 6.5.1 to 6.5.2
Working with MAVEN_OPTS has changed again. Hopefully for the last time within the 6.5.x iteration. (see http://youtrack.jetbrains.net/issue/TW-17393)
Now TeamCity acts as follows:
1. If MAVEN_OPTS is set TeamCity takes JVM arguments from MAVEN_OPTS
2. If "JVM command line parameters" are provided in the runner settings, they are taken instead of MAVEN_OPTS and MAVEN_OPTS is overwritten with this value to propagate it to nested Maven executions.
Those who after upgrading to 6.5 had problems of not using MAVEN_OPTS and who had to copy its value to the "JVM command line parameters" to make their builds work, now don't need to change anything in their configuration. Builds will work the same way they do in 6.5 or 6.5.1.
Changes from 6.5 to 6.5.1
(Fixed known issue) Long upgrade time and slow cleanup under Oracle
Changes from 6.0.x to 6.5
(Known issue) Long upgrade time and slow cleanup under Oracle
On first upgraded server start the database structures are converted and this can take a long time (hours on a large database) if you use Oracle external database (TW-17094). This is already fixed in 6.5.1.
With this version of TeamCity we added semi-automatic upgrade of JVM used by the agents. If there is a Java 1.6 installed on the agent, and the agent itself is still running under the Java 1.5, TeamCity will ask to switch agent to Java 1.6. All you need is to review that detected path to Java is correct and confirm this switch, the rest should be done automatically. The operation is per-agent, you'll have to make it for each agent separately. Note that we recommend to switch to Java 1.6, as at some point TeamCity will not be compatible with Java 1.5. Make sure newly selected java process has same firewall rules (i.e. port 9090 is opened to accept connections from server)
IntelliJ IDEA Coverage data
Coverage data produced by IntelliJ IDEA coverage engine bundled with TeamCity 6.5 can only be loaded in IntelliJ IDEA 10.5+. Due to coverage data format changes older versions of IntelliJ IDEA won't be able to load coverage from the server.
IntelliJ IDEA 8 is not supported
Plugin for IntelliJ IDEA no longer supports IntelliJ IDEA 8.
Unsupported MySQL versions
Due to bugs in MySQL 5.1.x TeamCity no longer supports MySQL versions in range 5.1 - 5.1.48. TeamCity won't start with appropriate message if unsupported MySQL version is detected. Please upgrade your MySQL server to version 5.1.49 or later.
Finish build properties are displayed
Finished builds now display all their properties used in the build on "Parameters" tab. This can potentially expose names and values of parameters from other builds (those that the given build uses as artifact or snapshot dependency). Please make sure this is acceptable in your environment. You can also manage users who see the tab with "View build runtime parameters and data" permissions which is assigned "Project Developers" role by default.
PowerShell runner is bundled
If you installed PowerShell plugin manually, please remove it form
.BuildServer/plugins as a fresh version is now bundled with TeamCity.
Changed settings location
- XML test reporting settings are moved from runner settings into a dedicated build feature.
- "Last finished build" artifact dependency on a build which has snapshot dependency is automatically converted into dedicated "Build from the same chain" source build setting.
Responsibility is renamed to Investigation
A responsibility assigned for a failing build configuration or a test is now called investigation. This is just a terminology change to make the action more neutral.
If you have any email processing rules for TeamCity investigation assignment activity, please check is they need updating to use new text patterns.
REST API Changes
Several objects got additional attributes and sub-elements (e.g. "startDate" in reference to a build, "personal" in a change). Please check that your parsing code still works.
In previous releases, if you have specified build checkout directory explicitly using absolute path, TeamCity would not clean the content of the directory to free space on the disk.
This is no longer the case.
So if you have absolute path specified for the checkout directory and you need the directory to be present on agent for other build or for the machine environment, please set
system.teamcity.build.checkoutDir.expireHoursproperty to "never" and re-run the build. Please take into account that using custom checkout directory is not recommended.
If you are using one of system.teamcity.build.checkoutDir.expireHours properties and it is set to "never" to prevent the checkout directory from automatic deletion, the directory might be deleted once after TeamCity upgrade. Running the build in the build configuration once after the upgrade (and within 8 days from the previous build) will ensure that the directory preserves the "protected" behavior and will not be automatically removed by TeamCity.
Free disk space
This release exposes Free disk space feature in UI that was earlier only available via setting build configuration properties.
While the old properties still work and take precedence, it is highly recommended to remove them and specify the value via "Disk Space" build feature instead. Future TeamCity versions might stop to consider the properties specified manually.
Command line runner
@echo off which turns off command-echoing is added to scripts provided by "Custom script" runner parameter. To enable command-echoing add
@echo on to the script.
Windows Tray Notifier
You will need to upgrade windows tray notifier by uninstalling it and installing it again. Unfortunately, auto-upgrade will not work due to issues in old version of Windows Tray Notifier.
- In earlier TeamCity versions Maven was executed by invoking the 'mvn' shell script. You could specify some parameters in MAVEN_OPTS and some in UI. Maven build runner created its own MAVEN_OPT by concatenating these two (
%MAVEN_OPTS%+jvmArgs). In this case, if some parameter was specified twice - in MAVEN_OPTS and in UI, only the one specified in MAVEN_OPTS was effective. Starting with TeamCity 6.5 Maven runner forms direct java command. While this approach solves many different problems, it also means that MAVEN_OPTS isn't effective anymore and all JVM command line parameters should be specified in build runner settings instead of MAVEN_OPTS.
- Those who had to manually setup surefire XML reporting for Maven release builds in TeamCity 6.0.x because otherwise tests weren't reported, now can forget about that. Since TeamCity 6.5 surefire tests run by release:prepare or release:perform goals are automatically detected. So don't forget to switch surefire XML reporting off in the build configuration settings to avoid double-reporting!
Email sending settings
Please check email sending settings are working correctly after upgrade (via Test connection on Administration > Server Configuration > EMail Notifier). If no authentication is needed, make sure login and password fields are blank. Non-blank fields may cause email sending errors if SMTP server is not expecting authentication requests.
Open API Changes
Several return types have changes in TeamCity open API, so plugins might need recompilation against new TeamCity version to continue working.
Also, some API was deprecated and will be discontinued in later releases. It is recommended to update plugins not to use deprecated API.
See also Open API Changes
Changes from 6.0.2 to 6.0.3
No noteworthy changes
Default memory options change
We changed the default memory option for PermGen memory space and if you had
-Xmx JVM option changed to about 1.3G and are running on 32 bit JVM, the server may fail to start with a message like:
Error occurred during initialization of VM Could not reserve enough space for object heap Could not create the Java virtual machine.
On this occasion, please consider either:
- switching to 64 bit JVM. Please consider the note.
- reducing PermGen memory via
-XX:MaxPermSizeJVM option (to previous default 120m)
- reducing heap memory via
Vault Plugin is bundled
In this version we bundled SourceGear Vault VCS plugin (with experimental status). Please make sure to uninstall the plugin from .BuildServer/plugins (just delete plugin's zip) if you installed it previously.
If you used standalone plugins that are now bundled in 5.0, do not forget to remove the plugins from
The newly bundled plugins are:
- Git (JetBrains)
- REST API (was provided with YouTrack previously)
If you use any plugins that are not bundled with TeamCity, please make sure you are using the latest version and it is compatible with the 5.0 release. e.g. You will need the latest version of Groovy plug and other properties-providing extensions.
Pre-5.0 notifier plugins may lack support for per-test and assignment responsibility notifications.
Database Settings Move
Move your database settings from the
<TeamCity installation folder>/ROOT/WEB-INF/buildServerSpring.xml file to the
database.properties file located in the TeamCity configuration data directory (
<TeamCity Data Directory>/config).