TeamCity Cloud

Développez des logiciels plus rapidement et avec moins de bugs.

Publié par JetBrains
Distribué par ComponentSource depuis 2007

Prix à partir de : $ 176.40 Version : 2025.07 Mise à jour : May 3, 2025

Capture d'écran de TeamCity Cloud
i

Looking for TeamCity hosted by you? Please see TeamCity On-Premises.

TeamCity Cloud 2022.10.x

Released: Oct 27, 2022

Mises à jour de 2022.10.x

2022.10.3

Updated Mar 21, 2023

Fixes

  • Improved the log message when a port for the HTTPS connection is busy.
  • .NET custom step exiting with 1 doesn't fail the build.
  • NuGet feed cleared after upgrading from 2022.10.1 to 2022.10.2.
  • Update Git version within TeamCity Docker Images: 2.39.1 -> 2.39.2.
  • Kotlin DSL generates excessive UI Patch for 'branchFilter' VCS option parameter.
  • Build can fail with "Unable to collect changes" error if VCS generic executor pool queue is full.
  • Set focus on first found runner when searching for build runners.
  • Failed to upload certificate: Invalid key.
  • Vacuum of custom_data_body table can take too much time if there is a huge number of dead tuples.
  • Lots of logs "Failed to find agent type for agent ..." in teamcity-server.log after removal of a non cloud agent.
  • Null pointer exception calling buildQueue API since upgrade to build 117025.
  • Docker processes left after builds.
  • Cannot login to docker repository due to a file lock on windows.
  • Docker_in_docker does not restart reliable.
  • Test metadata is not reported for finished tests in different flow id with test batching enabled.
  • "Add build step" button looks excess in "New Build Step" dialog.
  • Not all symbols in runner descriptions are processed correctly in grid view.
  • Build approval: improvements for the "Approval rules" field validation.
  • HTTPS: display a dedicated error message when a key has a valid format but is encrypted.
  • A lot of memory is consumed by FlowAwareIndexFileOptimizedBuilder.
  • Contention on storing newly loaded VCS commits from the database can slow down startup of the server.
  • Four security problems have been fixed.

2022.10.2

Updated Feb 3, 2023

Features

  • Improved HTTPS settings.
  • Improved AWS support.
  • Improved Perforce integration.

2022.10.1

Updated Dec 1, 2022

Features

  • Now supports custom SSL certificates for native Git.
  • Added support for NUnit console 3.16.

2022.10

Updated Oct 27, 2022

Features

  • Sakura UI
    • Sakura UI is now the default in this release - The Sakura UI is modern, beautiful and fast. Built with accessibility in mind, it has feature parity with the classic UI, and also brings many new unique capabilities.
  • Cloud Improvements
    • Easier and more secure management of AWS credentials - Added a new AWS credentials management system that issues temporary, short-lived AWS keys and exposes them in a safe way for your builds.
    • Terminal access to AWS EC2-based build agents - To improve the debugging experience of cloud CI/CD, the ability to open a secure terminal session to AWS EC2-based build agents directly from the TeamCity UI has been added - without the need to access the cloud provider’s management console or ask a busy DevOps team to set up network access lists and SSH key-pairs.
      • The availability of the feature is controlled by the “Open an interactive session to the agent” permission that is only enabled for server administrators by default but can be assigned to other users when needed.
    • Cloud agent maintenance mode - Added new maintenance mode. In this mode, TeamCity does not automatically terminate cloud agents after the build is finished, and they don’t get allocated for running new builds, allowing you to do the troubleshooting.
    • Managing cloud instances in a multi-server setup - Starting with this release, secondary nodes of TeamCity can start and stop cloud instances, providing uninterrupted operation of cloud-based CI during maintenance of a primary server.
  • Enhanced VCS Integrations
    • Perforce - This release comes with two improvements related to integration with Perforce tools:
      • Perforce Shelve Trigger now understands when a shelved changelist is related to a non-default stream and allows the build to be run on it.
      • TeamCity now detects changelists that have reviews in Perforce Helix Swarm and adds links to the respective review and change pages in Build Overview and Changes pages, respectively.
    • Support for refresh tokens in OAuth connections - TeamCity now uses short-lived OAuth tokens when working with GitLab, Bitbucket Cloud and Microsoft Azure DevOps, allowing you to create VCS roots without having to manually generate access tokens for these services.
  • Next-Level Security
    • Out-of-the-box HTTPS support - Added the ability to enable HTTPS for your TeamCity server. All you need to do is to upload a HTTPS certificate, or a certificate chain, in PEM format, and TeamCity will do the rest.
    • Restricted access tokens - You can now create temporary access tokens that will allow other people to log into TeamCity under your account, but with a limited scope of permissions, for example, with view-only access for one specific project. This can be useful in cases where you want someone to help you debug your pipeline, or when making a demo.
  • Authenticate using Your Google Account
    • To support more workflows and make the experience with TeamCity smoother, authentication using Google accounts is now supported.
    • When logging in with Google, TeamCity will instantly match the Google email with an existing TeamCity user, and log them in without having to enter a password.
    • It can also automatically create new profiles when new members join your team, provided that their email addresses belong to one of the domain names you specified.
  • Improved Disk Space Cleanup
    • The Free Disk Space build feature now keeps track of the size of artifacts and automatically calculates the disk space required for resolving artifact dependencies.
    • This makes the use of the build feature more straightforward, as you no longer have to know the size of the artifacts downloaded during the build, and the only thing you need to specify is the amount of disk space required for the build process itself.
  • Promotion of Personal Builds
    • Added the ability to promote personal builds. Builds that are triggered after the promotion also become personal builds.
Back to TeamCity Cloud Releases