Some features in this build may require manual reconfiguration of your builds.
If your database configuration differs from default HSQLDB settings, you'll have to configure database in a separate database.properties file. This file should be located in the TeamCity data config directory (defaults $HOME\.BuildServer\config). After the first run of TeamCity template files database.mysql.properties and database.hsqldb.properties are be placed to this directory for reference. Copy one of them to database.properties and edit settings according to your database configuration.
TeamCity provides enhanced dialog to setup builds which depend on IntelliJ IDEA's IPR project file. Unfortunately, it was impossible to convert old configuration to the new one, so after upgrade to this version of TeamCity you'll have to tweak your configuration manually.
To do it, visit build configuration page/build runner section. The first visit to this page may be slow, because TeamCity will download and analyze all project module (*.iml) files to detect used global libraries, path variables, jdk and so on. Subsequent visits will be much faster.
This page will provide options to configure project JDK, path variables, global libraries. If some module files could not be obtained from VCS, this will be shown as well.
There is no more agentd.exe in the new agent installation.
To run service user can use <agent>/bin/service.start.bat
To stop service user can user <agent>/bin/service.stop.bat
To install service <agent>/bin/service.install.bat
To uninstall service <agent>/bin/service.uninstall.bat
Installed agent will still use agentd.exe. Auto updates should work correctly as well. But, to migrate to the new service wrapper user should reinstall agent explicitly.
Using new service wrapper allows user to change any agent JVM parameters.
To upgrade agent from agentd service to java service wrapper:
Agent process will have a name TeamCityAgentService-windows-x86-32.exe
To work with net.exe utility please use the name TCBuildAgent. For
net start TCBuildAgent - start agent
Now we use new format for links to build artifacts. The change was done to support Ivy and dependent builds (see below). The documentation for the new format is available here.
TeamCity plugin works with Eclipse 3.2+ and requires plugin Subclipse 1.2.0.
Eclipse plugin for TeamCity features:
Both watched projects and changes views display TeamCity builds and build configuration statuses, allow to open build log of selected build in Eclipse. Cumulative watched projects and remote run builds statuses are displayed in Eclipse status bar.
TeamCity allows to depend one build configuration on another one in terms of artifacts. I.e. if one build configuration requires library produced by another build configuration, you can easily add such dependency and dependent library will be downloaded to the specified place right before build start.
Moreover, TeamCity artifacts repository acts as Ivy repository, so you can reference and use artifacts from TeamCity in your ant builds!
If your build produces some HTML/text/image report which is available as artifact of your build, you can easily create a custom report tab which will show your report embedded right to TeamCity. To do it:
<report-tab title="A Report" basePath="report.zip" startPage="index.htm" /> <report-tab title="A Report2" basePath="reportDir" startPage="index.html" />
From now, duplicates results are available in the Web UI. You can easily open file with duplicates in IDE, by clicking the link near file with duplicate.
Now you can see the current status of the change, not only the first one. See screenshot.
TeamCity data directory can be configured in two ways:
The default value for TeamCity data directory is $HOME/.BuildServer where $HOME points to user's home directory.