v9.1 [Aug 7, 2015]
Reproduce any of your builds at any point in time, dated back to as long ago as your VCS allows. Store different build steps and parameters in different branches, and apply them when needed, in any way you need. TeamCity 9.1 comes with enhanced NUnit support: not only is the latest NUnit 3.0 supported in TeamCity NUnit runner, but NUnit also detects if it is run by TeamCity. This provides guaranteed compatibility with all upcoming features of NUnit and TeamCity. TeamCity 9.1 comes with unidirectional Agent-Server communication which adds an extra level of security for your build agents. It simplifies your firewall configuration by eliminating the insecure, HTTP connection from the server to agent, making it possible to use HTTPS protocol only. Change the order of your projects and build configurations on the Projects Overview page to better reflect your actual projects' structure.
v8.1 [Mar 19, 2014]
- List process details in swabra report for processes locking checkout directory
- Allow to limit maximum size of the build queue
- Print JVM parameters on server/agent start into the log
- AssumptionViolatedException interpreted as a failure by TeamCity
- "Failed to start build" errors are displayed on VCS Roots administration page
- Artifact Cache is not cleaned if it's not on the same drive as "temp" and "Build Checkout" folder
- Deleting projects from disk when there are queued builds in the projects is not processed gracefully
- Update copyright year in the Windows tray notifier about screen
- Diff View: wrong line can be highlighted as changed
- .NET Inspections runner crashes for solutions containing SpecExplorer section
- Wrong (reset) launched time for cloud instances after cloud profile editing
- JavaScript injection via URL parameter on Cancel button click
- Build with Gradle with parallel-threads=4 failed
- TeamCity Inspections result in large number of invalid "errors"
- "VCS problem" error is shown on VCS roots list for unrelated VCS root
- VS Addin. Local Changes view is not updated after changes are commited into TFS 2013.
- Slow opening of edit build report tab dialog
- Incorrect handling of 0 quota in SharedResources
- IndexOutOfBoundsException in BuildQueuePriorityOrdering.updateMovedItemsPriorities
- Easy DB setup: MSSQL integrated authentification stops working after first attempt
- VCS revisions on agent use conflicting file names for checkout directories with non-latin names
- MS SQL JDBC: We recommend to use the native MS SQL JDBC driver, but the database.properties template file contains URL template for JTDS.
- teamcity is hanging after a build configuration renaming
- Team City RSpec formatter fails under RSpec 3
- REST API: You do not have enough permissions to access VCS modification
- Make server memory warnings which do not indicate actual performance degradation hidable
- Agent can hang after OutOfMemoryError: Java heap space
- Unknown Perforce VCS roots are showing up in the VCS log
- Build with a full patch but doesn't remove old files on the agent
- NoClassDefFoundError for Eclipse 3.8 and TeamCity Eclipse plugin
- triggers save the input values despite the Cancel button was pressed
- Improve memory usage exceeded message for permgen
- Artifact resolving fails while cleanup is in progress: IOException - Failed to download ... Illegal status [503] while downloading
- Security issue - any Project Admin can grant System Admin role to any other user
- "Current TeamCity memory usage" shows only old gen memory usage
- Automatic merge does not indicate if there is a problem pushing merge result to the repository
- Publishing files to artifacts cache ignores size limit
- Can not disable publishing to artifacts cache
- Maven metadata provider tries to resolve unused parameter
- Custom Run dialog is broken
- Overtime icon pointing to the wrong resource when not running TC on the domain root
- Agent java.lang.OutOfMemoryError: PermGen space
- Ruby Environment Configurator does not find Ruby in PATH
- No ReSharper Properties for Folders and Projects
- Cloud: Terminate Instance after first build finished not working
- Error parsing MSTest trx report: IllegalArgumentException: Null blockName, at all
- Notification popups are not working in tray notifier
- A build in the queue can be listed with state="unknown"
- Eclipse plugin splits commit
- Error indexing changes for build: UnsupportedOperationException: Method getVcsRoot() cannot be called for personal build
- "Failed to decrypt data." error for password fields in custom run build dialog
- Problems & tests tab does not show neither tests nor build problems
- Different revisions of the same root in a single build chain
- REST API: Modifying user's groups is ineffective: first removes from all groups and then adds
- NoRunningBuildException in agent log
- maintainDB.cmd uses default JVM heap memory settings on first run
- Cancel button in meta runner editor is not working
- Using dotCover in NUnit or MSpec runner brings .NET 3.5 agent requirement
- Unclear errors on LDAP users synchronization: "The specified username ... is already in use by some other user." and " [Assertion failed] - this expression must be true"
- Absolute paths (with wildcards) stopped to work for XML reports
- Backup (from UI) of plugin data warns on missed files
v6.5 [May 27, 2011]
TeamCity Professional Edition is now rid of many previous limitations. Small and medium development teams can now run FREE TeamCity with an unlimited number of registered users, support for LDAP and NT authentication, and adjustable per-project permissions.
With this change we aim to make TeamCity even more affordable for many teams and startups.
TeamCity introduces new means to mute some of the failing tests so they wouldn't affect build status, allowing to significantly reduce cluttering of the build information flow.
This feature is especially useful when some tests fail for a well known reason, but it is currently not possible to fix them. This could be inability to fix test soon, tests which are written before functionality, or so-called 'flickering' tests.
Muting tests is a potentially dangerous operation, that is why it is only available for Project Administrator role by default.
Grouping tests by package is an essential feature for faster problem investigation.
Tests can now be grouped in TeamCity on the build results page, current problems page, my changes page and so on.
TeamCity 6.5 provides a new, experimental way to remotely install build agents on the machines in your network, or in the cloud.
TeamCity can now push the agent software to either Unix (by SSH) or Windows (with help of Sysinternals psexec) machine. Agent is also configured there to run on startup.
Remote Agent installation integrates with Amazon EC2 Cloud nicely too. TeamCity can automatically push agent software upon on-demand EC2 agent instance creation.
TeamCity 6.5 provides a more natural way to start Personal Builds on server with distributed version controls.
If you are using Git or Mercurial, you can configure any specific build configuration to trigger Personal Build on any commit in one or multiple VCS branches. For watching multiple branches, TeamCity uses name pattern match.
