TeamCity 2022.04: Parallel Tests, Improved Integration with Amazon AWS, Built-in Code Quality Analysis, Updated VCS Integrations, and more
TeamCity 2022.04 introduces the new Parallel Tests feature that delivers an extraordinary speed boost when testing your projects. New powerful code analysis features will cut the time you spend on code reviews and increase the maintainability of your projects. Users who run their builds in the cloud will love the improved integration with Amazon S3 and Amazon CloudFront, as well as the new option of managing Cloud Profiles programmatically. There are a number of improvements to VCS integrations, new configuration options, and many great updates to the user interface. Unparalleled Sp
TeamCity 2021.2: Two-factor Authentication; Improved Integrations with Perforce Products, JetBrains Space, and Azure DevOps; a New Cross-Platform C# Script Runner; and Updates to the Sakura UI
TeamCity 2021.2 features 2FA, improved integrations with Perforce, JetBrains Space, and Azure DevOps, and a new cross-platform C# Script runner.
TeamCity 2021.1.1 is here
TeamCity version 2021.1.1 is released. This update resolves over 90 big and small issues. Plenty of them are related to improving the newly released features (such as Node.js runner and Elasticsearch) and fixing the build log representation in our experimental UI. Other prominent improvements are: Regression fixes for 2021.1:Fixed the behavior when subprojects were ignored in project settings committed to a VCS in XML format.Fixed a bug in the NuGet performance optimization algorithm. Trying to load a package whose filename contains the "." (dot) symbol would fail and result in the "Coul
TeamCity 2021.1: Kotlin and Node.js Build Runners, Trigger-Defined Parameters, High Availability, and more
TeamCity 2021.1 brings brand-new build runners for Kotlin and Node.js, improves integration with Perforce, and enables a whole range of new workflows by allowing build triggers which define parameters to be used inside build scripts. Users with demanding availability requirements will love the new option to transfer main server responsibilities to secondary nodes in the runtime with minimum downtime. There are also multiple updates to the Sakura UI that will make your work with TeamCity easier, faster, and more enjoyable. (more…)
Introducing TeamCity Cloud – A Managed CI/CD Service by JetBrains
Everything you love about TeamCity – now hosted by us! Today we’re launching TeamCity Cloud – a cloud version of TeamCity that we’ve been developing for almost two years. TeamCity Cloud is a managed CI/CD service that is designed for teams that don’t want to deal with maintaining and scaling their own infrastructure. After 14 months of extensive beta testing, it is now officially ready and can be used in real production environments – we invite you to try it out! Sign up for TeamCity Cloud This release was made possible not only by the hard work of many teams inside JetBrains, but also by a
TeamCity 2020.2.4 is here
TeamCity version 2020.2.4 is released. This bugfix update resolves over 30 various issues and optimizes the TeamCity performance. We strongly recommend upgrading as it also brings multiple security improvements. The full list of fixes is available in our release notes. This might be the last bugfix update for TeamCity 2020.2. Meanwhile, we are actively working on our next major release. You can already take a look at some of its features provided in the scope of our Early Access Program. Stay tuned for more updates coming soon! As any minor update, 2020.2.4 shares the same data format with all
TeamCity 2020.2.3 is here
TeamCity version 2020.2.3 is released. 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 to go and reconfigure the VCS root settings. If you prefer the users of your TeamCity server to authenticate through third-party services (for example, GitHub), you can now globally hide the default
TeamCity 2020.2.2 is here
TeamCity version 2020.2.2 is released. Note: The release candidate build of this version was shortly available for download yesterday. If you have already upgraded to that build (85882), 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 120 bug fixes and improvements. Many of these fixes aim at optimizing and polishing our Sakura UI. This version also adds a couple of new experimental UI features: The reworked Build Queue page is now displ
New in TeamCity 2020.2: Short-Lived Access Tokens
TeamCity 2020.2 now supports short-lived access tokens, which can expire automatically after a specified time period. They are perfect for shareable command-line scripts or demos, when you don’t want to remember to go back to the UI to delete your token. Watch the feature in action: For more details on how TeamCity’s access tokens work, have a look at our documentation.
New in TeamCity 2020.2: Bitbucket Cloud Pull Requests
TeamCity 2020.2 finally comes with integration for Bitbucket Cloud pull requests. 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. Watch this screencast to see the “Bitbucket Cloud Pull Request” feature in action. For more details on how TeamCity’s pull request support works, have a look at our documentation.
New in TeamCity 2020.2: Python Build Runner
TeamCity 2020.2 comes with first-class native Python Support, and you no longer need to use a third-party plugin to build your Python projects. 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. Use Kotlin DSL to configure your Python build steps. In addition, the Python runner integrates tightly with TeamCity just like all other TeamCity runners. You can track changes, analyze failures, a
TeamCity 2020.2.1 is out
Today we are releasing the first bugfix for TeamCity 2020.2. Version 2020.2.1 brings more than 140 improvements. 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. We strongly recommend upgrading as this TeamCity version resolves a few security problems as well. The full list of fixes is available in our release notes. As any bugfix update, 2020.2.1 shares the