Child pages
  • Gaya 8.1 EAP1 (build 29353) Release Notes

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

MS Visual Studio 2013 support in build runners

MSBuild and Visul Studio Solution build runners now have full support for Microsoft® Visual Studio 2013 and Microsoft® Build Tools 2013. Support for the new version of Visual Studio in the TeamCity Add-in and MSTest build runner will be added in the future versions.

Note

This EAP build does not have a license key bundled with it, please use the license key from EAP download page.

Wiki Markup
{hidden-data}{note}You can download the new TeamCity 8.0 EAP from [EAP download page|TW:Download Latest]{note}{hidden-data}

Table of Contents

Auto merge build feature

If you are using feature branches with Git and Mercurial, with the help of "Automatic Merge" Build Feature you can now configure TeamCity to merge a feature branch automatically to the master if a build in the feature branch completes successfully.

hidden-data


h2. Simple/advanced options on build configuration settings

Build configuration and VCS root settings are divided into simple and advanced options.

There is also an option to merge manually form the build's Changes tab.

Image Added

VCS labeling build feature

A new build feature for VCS labeling was added. VCS labeling settings will be converted automatically to this build featureVCS labeling settings were reworked as a Build Feature instead of options in the VCS Settings section. The existing settings are converted automatically to the new format. The build feature allows for more flexible configuration, : you can now have different labeling settings for different VCS roots, or overwrite the labeling settings inherited from a template completely.

Image Added

Project-level settings

Build results report tabs moved to project level

In previous versions there were two places where you could configure report tabs:

  • project level report tabs were configured

...

  • under project settings
  • build results report tabs were configured

...

  • as "Report Tabs" global server settings

Now both project-level and build-level report tabs are configured on the project level; thus project administrators can manage build report tabs themselves.
Server-wider build-level report tabs are automatically moved under the Root project settings.

Maven settings moved to project level

These settings have Configuration of Maven profiles (settings.xml) has also been moved from the global administration area to the project level, the "Maven Settings" tab. This makes it possible to delegate configuring Maven settings to project administrators.

JaCoCo coverage integration

...

Configuration simplification

The Create build configuration wizard is no longer available. It is replaced with a simple dialog asking for the build configuration/template name and ID and creating the build configuration right away.

Build runner settings improvements

You can now list available targets/tasks, IntelliJ IDEA run configurations and inspection profiles right on the build step pagewhen defining build steps in the administration UI.
For Java based runners, there is a Java selection versions drop-down with versions of Java detected on available agents.

Build runners auto discovery

The new "Auto-discover" button on the Build Steps page of a build configuration starts a process that attempts to determine the build runner settings by scanning the VCS repository of the build configuration. For now, auto discovery works for Ant, Maven, Xcode, Visual Studio solution, MSBuild runners and IntelliJ IDEA based projects. More options will be available in subsequent EAP builds.

Advanced options are hidden by default

To reduce complexity of the user interface, many options on the build configuration and VCS root settings pages are now hidden by default. You can access them by clicking the "Show advanced options" link.

MS Visual Studio 2013 support in build runners

MSBuild and Visual Studio Solution build runners now have full support for Microsoft® Visual Studio 2013 and Microsoft® Build Tools 2013.
Support for the new version of Visual Studio in the TeamCity Add-in and MSTest build runner will be added in the next EAP.

JaCoCo coverage integration

A new coverage engine based on JaCoCo is now available for Ant, Maven, Gradle and IDEA Project build steps.

New server health reports

Some new health reports were added to:

  • report to detect suitable problems with reusing builds reusing problems for configurations with snapshot dependencies
  • report detecting detect queued builds sitting in the queue without compatible agents
  • report for cloud agent issues (the agent machine cannot be stopped, or an agent is in the idle state longer than the timeout)
  • detect exhaustion of the server disk space and pause the build queue in such a case

Additionally, some of the health reports that do not require administrator's permissions are now available in the user space, on the build configuration home page.

Other improvements

  • memory usage of the TeamCity server has been reduced for the cases when builds have tens of thousands of testschanging of IDs of a build configuration, project or VCS root does not invalidate bookmarked links with previous IDs
  • statistic values published during the build are now shown on the Build Parameters tab
  • projects names in the UI got drop-down menus with all the sub-tabs and the "Edit Settings" link for quick navigation. Build configurations now also list all the sub-tabs in their drop-downs
  • a project can be changed selected in the investigation dialog when an investigation is assigned for a test, . This is useful when the test fails in sibling projects
  • tabs with projects have been replaced with a drop-down on the My Changes page
  • statistic values published during the build are now shown on the Build Parameters tabmemory usage of the TeamCity server has been reduced for the cases when builds have tens of thousands of tests
  • My Changes page now uses a drop-down for projects instead of tabs
  • a new option in YouTrack integration picks all project IDs allows for monitoring all projects from the YouTrack server automatically
  • the cron schedule trigger has got the timezone setting too
  • TeamCity keeps track of previous IDs of a build configuration/project or VCS root, and if ID changes object is still accessible by previous ID
  • create build configuration wizard is no longer available. It is replaced with a simple dialog asking for the build configuration/template name and ID.
  • for the cron-based trigger
  • A new build parameter is introduced to pass user who triggered the build into the build script
  • Shared resources plugin improved to pass all the taken locks into the build. Please check the related upgrade notes entry
  • NuGet 2.7 packages restore is supported
    See also full list of resolved issues