Download old versions of teamcity

Windows installer Archive with bundled Tomcat any platform Java EE container war - not recommended, use distribution with bundled Tomcat instead. Release date: 24 July Build Windows installer Archive with bundled Tomcat any platform Java EE container war - not recommended, use distribution with bundled Tomcat instead.

Release date: 21 June Build Windows installer Archive with bundled Tomcat any platform Java EE container war - not recommended, use distribution with bundled Tomcat instead. Release date: 17 May Build Windows installer Archive with bundled Tomcat any platform Java EE container war - not recommended, use distribution with bundled Tomcat instead. Release date: 13 March Build Windows installer Archive with bundled Tomcat any platform Java EE container war - not recommended, use distribution with bundled Tomcat instead.

Release date: 31 January Build Windows installer Archive with bundled Tomcat any platform Java EE container war - not recommended, use distribution with bundled Tomcat instead.

Release date: 20 December Build Windows installer Archive with bundled Tomcat any platform Java EE container war - not recommended, use distribution with bundled Tomcat instead.

Release date: 27 November Build Windows installer Archive with bundled Tomcat any platform Java EE container war - not recommended, use distribution with bundled Tomcat instead. Space shortcuts ChangeLog.

Child pages. Previous Releases Downloads. Browse pages. Pages Home. Icon This page is obsolete and no longer supported. You can al. The new release comes with over 80 fixes and improvements, including the following: When you create a project or build configuration from a Git repository URL, TeamCity will allow changing the default branch and branch specification right in the creation wizard.

If you actively use feature branches, you can now easily select them from the start, with no need. Note: The release candidate build of this version was shortly available for download yesterday.

If you have already upgraded to that build , we highly recommend that you upgrade to the release build today, as it contains additional fixes intended for the release. We apologize for the inconvenience this may cause. The new release comes with over bug. You can set up TeamCity to automatically detect pull requests made in your Bitbucket Cloud repository and run builds for them.

Together with the Commit Status Publisher and the Automatic Merge build features, this makes working with pull requests in Bitbucket Cloud really easy. It supports all popular Python build workflows: Run files, modules, or custom scripts.

Execute pytests or unittests. Run linters, like flake8 or pylint. Use virtual environments, like virtualenv or pipenv. Run your Python builds inside a Docker container.

Today we are releasing the first bugfix for TeamCity Version Remember to check our upgrade notes to read the details of the following important changes: Breaking change for Linux Docker images of the TeamCity server: running under a non-root user by default. NET runner change: corrected logic of processing parameters of the dotnet run command. It is useful whenever you want to call an external service during your builds that does not respond immediately, but takes an indefinite amount of time to run.