- Due to changed VCS settings hash calculation, all build configurations will perform clean checkout on the first run with this new build. The default checkout directories (hash) names will also be changed.
- Due to fixes in "Remember me" feature, all users will be logged out and will need to re-login after this new version installation. After the re-login, "remember me" will work as expected.
- Inspections and Duplicates build runners use 8.x (Diana) branch of InteliiJ IDEA, so there might be differences with the way 7.x IntelliJ IDEA works. If you believe the are regressions or issues with the runners, please report us about this.
Remote Run on the specified agent from IntelliJ IDEA
With TeamCity plugin for IntelliJ IDEA you can now select one or several Build Agents you want to run your personal build on. Such approach allows you to test your changes under the desired platforms, operating systems, databases, environment variables which are set for the Build Agent you specify.
Ability to redefine certain build parameters on manual build run
On "Properties and environment variables" page you can now opt to redefine the build parameters (environmental variables and system properties) when starting a build manually. The specified values of these parameters work as default ones.
When you start a build by pressing the "Run" button in the web UI, a dialog window appears allowing you to customize values of the build parameters.
Reworked plugin packaging
Server-side plugin can be provided as a bunch of JAR files, or as a single ZIP archive. Plugin files should be placed into the
<TeamCity data directory>/plugins/<plugin name> folder. In case of ZIP archive, plugin classes will be searched among all JAR files found in the archive.
Plugin name is taken from
<plugin name> folder or from the name (without extension) of the .ZIP file.
To get the plugin name or to map a plugin relative path to the context path, use
jetbrains.buildServer.web.openapi.PluginDescriptor class which can be required in bean constructor.
All plugin's classes are loaded to the same (non-Web Application)
ClassLoader. New Spring Application Context is created for every plugin.
Risk tests reordering support for NUnit
The feature is supported for the following build runners:
- sln2003, sln2005, and sln2008
If the risk tests reordering option is enabled, the feature for NUnit test runner works the following way:
- NUnit runs tests from the "risk" group using test name filter.
- NUnit runs all other tests using inverse filter.
- Performance improvements
- Shared items support
- More bug-fixing
Support for Diana (IntelliJ IDEA 8) EAP project file format
At last, TeamCity project itself has migrated to Diana's project format and uses it for own builds. New format is supported for Duplicates, Inspections, and Ipr build runners.
Ability to configure charts on Project home page (Statistics tab)
Now you can customize "Statistics" tab on the Project Home Page using one of the following approaches:
- Specify which standard charts should be shown on the page (TeamCity-provided ones, like coverage, inspections, duplicates)
- Configure custom charts to display on the Statistics tab.
Custom artifacts-based tab on the Project page
In TeamCity 3.x, it is possible to configure artifacts-based tabs for a build. In this EAP, we provide a possibility to add such a tab on the Project Home Page.
You can specify a rule for a build which artifacts data will be shown on the tab:
lastPinned or specific build.
Please refer to the online reference for detailed description.
Build Results improvements
- Build history shows whether the build is used in any other builds. Please note that if the build is used in any other builds, it will not be cleaned up until all those builds are removed from the build history.
- "Dependencies" tab of the build results now shows both builds from which artifacts were used and builds that used the artifacts of the current build. The list of individual artifacts used is also provided.
- Build Results page now has "Build Parameters" tab that displays the properties used by the build.
- "Tests" tab allows bi-directional sorting and was optimized for speed.
Build Agent management
- Ability to remove disconnected agents manually (by default, they will be removed automatically in 2 weeks after disconnection).
- Agents now have small bundled CPU benchmark and its results are displayed on the agent's details and "Connected Agent" table. Please note that the benchmark results can depend on the JVM version and options used by the agent. For example, '
-server' JVM option has a significant influence on the results. CPU benchmark also affects the way how the server distributes builds among agents. If a build duration estimate cannot be calculated for an agent (there were no builds in the history ran on this agent), TeamCity chooses fastest agent basing on CPU benchmark value.
- Agent authorization uses token-based principle to distinguish build agents when IP addresses are assigned with DHCP.
- Improved "All projects" control
- Clean up settings dialog has been reworked to allow easier configuration.
- NUnit tests runner reports test running
- Clean sources action from the Build Configuration Home page allows you to choose specific agents where to clean sources.