Child pages
  • TeamCity 3.1 EAP (build 6658) Release Notes
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

As we are approaching 3.1 release, this EAP represents the state of the TeamCity 3.1 as it will be released after a short stabilization period.

TeamCity 3.1 is a maintenance release with lots of bugs fixed and some minor features added.

New Notification Options: notify only on build state change

Now it is possible to receive notifications only when the build status changes. Two options are added: "Limit to only the first successful build after failed" and "Limit to only the first failed build after successful":

Agents Load Statistics

In order to better analyze TeamCity build agents load, we have introduced Agents load statistics that allows to visualize agents load during the specified time period:

More .Net Tools Support

Common NUnit tests

From now, following properties and environment variables are obsolete:

  • env.teamcity.dotnet.nunitlauncher1.1
  • system.teamcity.dotnet.nunitlauncher1.1
  • env.teamcity.dotnet.nunitlauncher2.0
  • system.teamcity.dotnet.nunitlauncher2.0
  • env.teamcity.dotnet.nunitlauncher2.0.vsts
  • system.teamcity.dotnet.nunitlauncher2.0.vsts
    Please use
  • env.teamcity.dotnet.nunitlauncher
  • system.teamcity.dotnet.nunitlauncher

New test runner supports several the following commandline:

where

  • v1.1 and v2.0 are version of .NET Framework to run tests
  • x86, x64 and MSIL are platforms to run tests, note, for .NET Framework 1.1 it only possible to use MSIL
  • NUnit-2.2.10, NUnit-2.2.9-VSTS and NUnit-2.4.6 are test frameworks to use

Note NUnit-2.2.9-VSTS is patched version of NUnit to run Microsoft Visual Studio Team System Tests (for Microsoft Visual Studio 2005)

NAnt improvements

There are several nant properties that are used by TeamCity <nunit2> task implementation:

  • 'teamcity.dotnet.nant.nunit2.failonfailureatend' - run all tests than fail if at least one test has failed.
  • 'teamcity.dotnet.nant.nunit2.platform' - values x86 or x64, sets desired runtime execution mode for .NET 2.0 on x64 machine.
  • 'teamcity.dotnet.nant.nunit2.version' - specifies version of NUnit runner to use. Available versions are:
    NUnit-2.2.10, NUnit-2.2.9-VSTS and NUnit-2.4.6. NUnit 2.2.10 is used by default
    We've also added support for NAnt 0.86 runner and NUnit 2.4 testing framework.
  • NUnit test runner will run tests in .NET Framework which is specified by NAnt target framework, i.e. on .NET Framework 1.1 or .NET Framework 2.0 runtime

Test categories are supported for <nunit2> task.

MSBuild improvements

NUnitTeamCity task now supports extra arguments:

  • 'Platform' with values x86 and x64 to specify desired runtime execution mode on x64 machine.
  • 'IncludeCategory' and 'ExcludeCategory'
  • 'NUnitVersion' specifies NUnit version to run tests. Available versions are:
    NUnit-2.2.10, NUnit-2.2.9-VSTS, NUnit-2.4.6. NUnit 2.2.10 is used by default

Sending Service Messages via Standard Output

As TeamCity reports tests on-the-fly and not after all the tests were finished, every testing framework needs it's own support for the feature.
In this release we are introducing an easy way to report running tests information to TeamCity: just print specially formatted message to the standard output of the build process and TeamCity knows there is a test!

Here is the list of supported service messages:

Please note that each message should be followed by a newline.

During-the-Build Artifact Publishing

Another cool feature of service messages is that now you can publish build artifacts, while the build is still running.
Just output the following line:
##teamcitypublishArtifacts '<path>'

And the files matching the "path" will be uploaded and visible as artifacts of the running build.

Please note that publishing artifacts process can affect the build because it consumes network traffic and some disk/CPU resources (should be pretty negligible for not large files/directories).

Artifacts that are specified in the build configuration setting will be published as usual.

UI Enchancements

Now you can navigate to any build configuration from any page. Projects tab has drop-down list:

And all the information of a queued build (start estimate, agent assignment) is now available right from the Projects page:

Enhanced External Database Support

  • Database migration tool now supports any direction migration
  • Initial support for Oracle is implemented. Please try on as-is basis.

Other Improvements

  • Build working directory setting
  • 3 levels of clean-up (artifacts, history, statistics)
  • Agent filter on build history
  • Quick search for build on specific agent
  • Ability to watch all projects
  • TLS support for e-mail sending
  • Build scheduling with CRON-like expressions
  • Tests time to fix statistics
  • Syntax highlighting in duplicates viewer
  • Basic support for reporting tests running in parallel (parallel ant task or TestNG)
  • "View Agent Details" permission (by default the permission is included in the Project Developer, Project Administrator, Agent manager and System administrator roles)
  • In Enterprise TeamCity version, Windows domain authentication is now available on Linux computers.
  • Duplicates and inspections browser now allows to browse results filtered by directories
  • No labels